Your flow cannot be found. Flow sys_id:n

[ShaibaazFaheem]

I am unable to open the flow when retrieving to the test instance from Dev. The error says 'Your flow cannot be found. Flow sys_id:n'
We work on three languages: English, Norwegian and Swedish. The flow is only accessible when the language is 'Norwegian'. It has no subflows attached. 

[vijaydodla]

This is a known data-translation issue in ServiceNow. The error occurs because the flow was originally created by a developer whose session language was set to Norwegian.

Because of this, critical metadata for the flow (specifically the Flow's Name) was only saved in the Norwegian translation tables. When a user with an English or Swedish session tries to open the flow, Flow Designer queries the database for the flow's name. Finding a blank/null value for those languages, the UI crashes and throws the "your flow cannot be found" error.

The easiest way to fix this is to update the base record directly from the backend list view while logged in with English.

1. Change your ServiceNow session language to English.
2. In the Filter Navigator, type sys_hub_flow.list and press Enter to open the Flows table.
3. Filter the list using the sys_id provided in your error message.
4. You will likely see the record, but the Name column will be completely blank.
5. Double-click the empty cell in the Name column and type the English name for the flow.
6. Save the change.
7. Repeat this process for Swedish (change session language to Swedish, go to the list view, and double-click to add the Swedish name). Once the name is populated for your current language, Flow Designer will be able to load the canvas without throwing the error.

 

To prevent this from happening again, always ensure your developers have their session language set to the system's base language (typically English) when creating new Flows, Tables, or Fields.

Once the base component is built in English, you can switch languages or use the Localization Framework to add the Norwegian and Swedish translations. Building structural components in a secondary language often leads to missing base-system references.

Please Accept the Solution if it works for you. This will help others to look at the accepted verified solution. Thank you ! 

[Tanushree Maiti]

Hi  @ShaibaazFaheem 

1) Refer: KB1709519 Resolving a flow cannot be found error in Flow Designer 

 

Resolution

Follow these steps to resolve the issue:

1. Use the right mouse button on the popup window displaying the error.
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 is used in your flow.
5. In the selected column, check for any invalid variable references.
6. Check other flow steps for references to deleted variables, noting that data pills may still display these as valid even when they're not.

2)KB0823104 Selecting the flow record from the flow designer fails: Flow "sys_id" Not found 

3) Refer: https://www.servicenow.com/community/developer-forum/quot-your-flow-cannot-be-found-flow-sys-id-an-q...

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