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

[jcmings]

Interesting! I haven't worked much with sub-flows using Get Catalog Variables. Thanks for sharing. Glad that we're at least approaching a fix...

[Ron28]

Thanks very much, just ran into this issue and your solution worked!

Ron

[Kim Sullivan]

For everyone's knowledge, I upgraded to Xanadu patch 6 and made sure Flow Designer was on the latest update and I'm still having this issue.  I opened a case with HI.  Will update this post when I get a solution.

UPDATE 2/27 - HI had me update to Flow Designer v26.3 and that repaired the issue.

[Lukas B]

On DEV, we had Flow Designer V26.3.5 which still had the issue.

An update to Flow Designer V26.4.1 resolved the issue. Thanks all!!

EDIT: Figured out that I've set a variable in a cat item to inactive and since I was using this variable in the flow, this caused the error. V26.4.1 showed me this in a nice warning UI message 🙂

[sk_24]

Thanks for the explanation @scottl,

It happened with me last week. I was adding "Assign Subflow Outputs" in the existing flow, which I created some time back, and after saving, it started throwing error.

I read it somewhere that this issue is related to "Get Catalog Variables" action. So, I removed this action and first added "Assign Subflow Outputs" and then "Get Catalog Variables", it helped me.