"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!

[Ehab Pilloor]

Hi @jcmings,

I was also facing this issue when making flow for Catalog Items. But found the Root Cause for this issue to be that when any variable name changes then this issue was occurring. When the change was reverted back, then I could open the flow. You can check if any changes was made to any field whose data pill is in the Flow for this. What I did was remove the variable, edit the name, then add back to the Flow.

Regards,

Ehab

[Martin Reintgen]

a deactivated variable can cause the same effect!

[Kim Sullivan]

As a best practice, I’m trying to get better about not pulling all my variables in from Get Catalog Item variables.  I’m trying to only pull the ones I need for future activities in the Flow.

[JulianP32954866]

But can still freak it out.

Good old WF just carried on and missed what the variable was, so may make it look odd, but at least it didn't freeze you out of the flow - which is what can happen.

Got a sys_id:Orp  today

Not sure why either, but repeatable,

I created a new output, assigned a value which is a Flow Variable and that is enough to kill it

Even if I tried to copy the Subflow and do the same in the new Subflow...

Processing 2 tables in the same flow

Table 1.  checks to see if a sys_id is passed, if so, store that in the Flow variable, otherwise create a record and do a few bits and then store that sys_id in the flow variable.

This existed, just not used this one

Table 2.  Ditto

The last action is was to set an output - table_two = the flow variable for table_two

THIS WORKS

add the action to set the output of table_one with the flow variable from table_one

THIS KILLS IT

I created a new  output, I removed the flow variable

saved

added a flow variable

saved

added an output

saved

Go to assign the flow variable to the output - Dead

It even has the gall to tell me it has saved but never releases the browser - and that is Edge, Chrome and FF.

[MananJ]

Hey folks,
Today I came across this error and resolved it as well.

Actually there was one variable which got deactivated but was used and referenced in the flow, so this was the cause of this error, so I activated that variable and the issue got resolved for me.
Hope this helps!
Kindly mark my answer helpful if it resolves anyone's issue as well