"Your flow cannot be found. Flow sys_id:An" error

[jcmings]

Sorry if this is the wrong place to put this -- but I ran into this issue the other day and couldn't find any guidance and wanted to post the solution that ended up working for me.

Problem: 

Whenever I open a specific flow in Flow Designer, I get the error "Your flow cannot be found. Flow sys_id:An." This prevents any changes to my flow from truly saving. 

Solution:

Many of the solutions I found online coached going to sys_hub_flow.list and pulling in the "Main snapshot" field and then pasting that sys_id into the URL of your errored out flow designer screen. While this allowed me to load the flow, it didn't recognize any changes I made. To finally resolve the error, I followed these steps:

1. In the Flow Designer landing page, right click the name of the flow causing issues and copy the sys_id
2. Navigate to sys_update_version.list and paste in the sys_id of my erroring flow
3. Revert to a previous (working) version of the flow

Other notes:

A lot of the posts I found online (mainly on these forums) discussed running into this issue when migrating a flow between environments. In most cases, users failed to move a sub-flow as well, and this caused issues. I happened to run into this error in a single environment, and I believe it's because I messed with the "Latest snapshot" field. 

Hope this helps!

[Joe1]

A build of Xanadu from December. Looks like the plugin may also be out of date.

[scottl]

SN has released the fix for it however you have to "upgrade" your instance to patch 5, before applying the update to the Flow designer plugin.  

So far I haven't had a flow corrupt  ...yet.

[Patrick Canary]

This just happened to me on a Flow I started designing today.  

My flow had a gather variables step.  At some point, I changed the name of one of the variables.  After that, I received the error.  Simply changing the variable back to the original name got rid of the error.  Once this was done, I temporarily removed the Get Catalog Variables step and all references to those variables (there weren't many), saved the flow, changed the variable name again to the new name, then reconstructed the Get Catalog Variables step.  It was a small pain, but at least I didn't need to redo the entire flow.

ServiceNow should implement some step to handle this.

[mohcine elbah]

Had a similar issue, updating the Workflow Studio plugin to the latest version fixed the problem.

[Jesse_H]

Thank you! This was the correct solution for me after migrating a large project with a new flow and flow actions (the flow causing this issue even uses get catalog variables).