The CreatorCon Call for Content is officially open! Get started here.

Flow Designer Error

Go to solution
Kumar54
Tera Contributor

3 weeks ago

I am seeing error for flow designer when i changed From one update set to another

Error:  " Your flow cannot be found. Flow sys_id:n"

0 Helpfuls
  • 993 Views
1 ACCEPTED SOLUTION

Go to solution
kaushal_snow
Mega Sage

3 weeks ago

Hi @Kumar54 ,

 

Error usually means Flow Designer can’t locate the flow snapshot record (often due to missing or corrupt sys_hub_flow_snapshot entries or broken references to subflows or variables)....a practical fix is to copy the flow’s sys_id, go to sys_update_version.list, revert to a previous working version, and verify that all referenced subflows, custom actions, and variables were migrated properly so the snapshot pointers align again....

 

If you found my response helpful, please mark it as ‘Accept as Solution’ and ‘Helpful’. This helps other community members find the right answer more easily and supports the community.

 

 

Thanks and Regards,
Kaushal Kumar Jha - ServiceNow Consultant - Lets connect on Linkedin: https://www.linkedin.com/in/kaushalkrjha/

View solution in original post

0 Helpfuls
6 REPLIES 6

Go to solution
Brad Bowman
Kilo Patron
Kilo Patron

3 weeks ago

I'm not following the changing of an update set, but I encountered this error when adding flow variables to an existing flow/subflow, and there are other causes.  The ultimate fix for the flow variable issue is to upgrade the Flow Designer plug-in to the latest version (fixed in v26.3 which requires Xanadu patch 5 or greater).  You can recover the last working version of the flow following these steps:

  1. In the Flow Designer / Workflow Studio main page that lists the flow/subflows/actions, click the information icon (i in a circle) beside the flow causing issues and copy the sys_id from the details shown.
  2. Navigate to sys_update_version.list and search on Names containing the sys_id
  3. Revert to a previous (working) version of the flow

Another possible workaround for opening a flow that already has this error is found here

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1709519 

 

0 Helpfuls

Go to solution
Kumar54
Tera Contributor

3 weeks ago

Tried above but no change

0 Helpfuls

Go to solution
RaghavSh
Kilo Patron

3 weeks ago

@Kumar54 Is this happening for other flows as well? If no then your flow has some illegal operation which is preventing that from getting saved.

 

Check your flow steps.

 

Also is your another update set in same scope as of flow?


Raghav
MVP 2023
LinkedIn
0 Helpfuls