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 ! 

[ShaibaazFaheem]

Hi @vijaydodla 

I tried searching with the sys ID, but no records found in the sys_hub_flow.list

[vijaydodla]

Hello  @ShaibaazFaheem ,

Could you search with the name of the Flow? Without an entry in the sys_hub_flow.list, there cannot be any flow present.

[ShaibaazFaheem]

@vijaydodla , the record is showing up but the name field is already populated. Please advise the next steps.