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

[Lakshmi Chettia]

I had the same error and checked i had overwritten the existing flow.

You can refer to the  KB - KB1709519  , if accessible 

OR

Follow these steps to resolve the issue:

1. Use the right mouse button to see inspect element on the popup window displaying the error. ( Content not found )
2. In the browser's developer tools, locate the HTML code: <div class="ReactModalPortal"> and remove it.
3. The flow should now be editable.
4. Go to where the "get Catalog variables" action update them and check for any errors and fix them
5. Check other flow steps for references to deleted variables, noting that data pills may still display these as valid even when they're not.
6. This should now allow you to Save/ Activate the flow and work as expected
7. Note: Clear Cache or login again to see the changes taking place

For me the above did a help a little but didn't fix the issue .So I  looked for an update set which had the entire flow from the past  from another sub instance and committed the same to bring back the flow.