Subflows must reference an existing, active flow in the same org in order to execute successfully. Salesforce prevents selecting unavailable or missing subflows in the Flow Builder UI, making this configuration impossible to create through the UI by default.
However, in unmanaged environments, flows can be modified or deployed outside the UI (for example, via Metadata API, source control, or incomplete deployments). In these cases, a flow may still contain a reference to a subflow that no longer exists, is inactive, or was never deployed.
This rule in Lightning Flow Scanner detects such invalid subflow references, which would otherwise cause runtime failures when the parent flow attempts to invoke the missing subflow. Affected flows should be corrected by restoring the referenced flow, activating it, or updating the subflow element to point to a valid flow.
Subflows must reference an existing, active flow in the same org in order to execute successfully. Salesforce prevents selecting unavailable or missing subflows in the Flow Builder UI, making this configuration impossible to create through the UI by default.
However, in unmanaged environments, flows can be modified or deployed outside the UI (for example, via Metadata API, source control, or incomplete deployments). In these cases, a flow may still contain a reference to a subflow that no longer exists, is inactive, or was never deployed.
This rule in Lightning Flow Scanner detects such invalid subflow references, which would otherwise cause runtime failures when the parent flow attempts to invoke the missing subflow. Affected flows should be corrected by restoring the referenced flow, activating it, or updating the subflow element to point to a valid flow.