Subflow not found: referenced subflow does not exist

A flow was imported from another instance without importing the required subflow dependencies, leaving broken references to non-existent subflows. (high likelihood)

The referenced subflow was deleted or deactivated after the parent flow was created, breaking the existing reference. (high likelihood)

The subflow reference uses an incorrect sys_id or name that does not match any existing subflow on the current instance. (medium likelihood)

The subflow exists but is in a different application scope and the parent flow does not have proper access permissions to reference it. (medium likelihood)

The subflow was moved to a different application scope after the parent flow was created, causing the reference to become invalid. (low likelihood)

Step 1: Navigate to Flow Designer and open the flow experiencing the error to identify which subflow reference is causing the issue.

Step 2: Check the System Log at System Diagnostics > Logs > System Log and filter by source 'Flow Designer' to find detailed error information including the missing subflow sys_id or name.

Step 3: Navigate to Flow Designer > Subflows and search for the referenced subflow by name or sys_id to confirm whether it exists on the current instance.

Step 4: If the subflow does not exist, check if it needs to be imported from another instance or created new, then import the missing subflow from the source instance or create a replacement subflow.

Step 5: If the subflow exists but is inactive, activate it by opening the subflow record and clicking the Activate button.

Step 6: If the subflow is in a different application scope, verify that the parent flow's application has proper access by checking Application Cross-Scope Access records or move the subflow to an accessible scope.

Step 7: Update the parent flow to reference the correct subflow by editing the subflow action and selecting the proper subflow from the dropdown or entering the correct sys_id.

Step 8: Test the flow by activating it and running a test execution to verify the subflow reference is now resolved correctly.