Resolving the ‘Flow sys_id:n Cannot Be Found’ Error in ServiceNow Flow Designer
In ServiceNow’s Flow Designer, encountering the error message “Your flow cannot be found. Flow sys_id:n” can occur under specific circumstances, particularly when:
- Using the “Get Catalog Variables” Action:
- Issue: There’s a known bug in Flow Designer where adding a “Get Catalog Variables” action, saving the flow, and then adding an “Assign” action can corrupt the flow. This corruption leads to the “Flow sys_id:n cannot be found” error. in
ServiceNow
- Issue: There’s a known bug in Flow Designer where adding a “Get Catalog Variables” action, saving the flow, and then adding an “Assign” action can corrupt the flow. This corruption leads to the “Flow sys_id:n cannot be found” error. in
- Missing Subflows in Update Sets:
- Issue: When a main flow includes a subflow that isn’t captured in the update set, and this update set is moved to another instance, the system cannot locate the subflow’s sys_id. This results in the error when attempting to access or execute the main flow.
Resolution Steps:
- For the “Get Catalog Variables” Action Issue:
- Avoid Specific Action Sequences: Be cautious when adding actions in Flow Designer. To prevent corruption, avoid the sequence of adding a “Get Catalog Variables” action, saving, and then adding an “Assign” action. If this sequence is necessary, ensure thorough testing to detect any issues early.
- For Missing Subflows in Update Sets:
- Include All Dependencies: When creating update sets, manually add all dependent subflows to ensure they’re included. After moving the update set to the target instance, verify that all components are present and correctly referenced.
Best Practices:
- Regular Backups: Regularly back up your flows and related components to prevent data loss in case of corruption.
- Thorough Testing: After making changes or moving update sets between instances, thoroughly test the flows to ensure they function as expected.
- Stay Updated: Keep abreast of ServiceNow updates and patches, as they may address known issues in Flow Designer.
By following these guidelines, you can mitigate the risk of encountering the “Flow sys_id:n cannot be found” error and ensure smoother operation within ServiceNow’s Flow Designer.
