An Error occurred while trying to load this flow. Try refreshing.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-30-2023 10:48 PM
I'm having a problem when I try to open a flow action, in a flow. Also, I can't access the flow variables in the same way, as catalog variables or other flow variables. Its stopping me from opening any flow action from this particular flow with the error as per below screenshot. Please provide any help or guidance on how to resolve this issue.
The flow was executing in the backend but when I opened this flow to make some changes it redirected to me for this error and this is happening in all the prod and subprod instances.
Get Catalog variables and other actions are missing
Thanks & Regards
-Sravani C

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-30-2023 11:47 PM
Hi,
Inspecting the system logs might give some answer as to why this error is occurring, the screen shot doesn't give any details.
But this sounds like something that might be a bug, try sending the details to ServiceNow support, and see if this has been fixed in later versions.
In worst case, the Flow is corrupt, and you will have to build a new one from scratch (or retrieve an earlier version from source control if you are using some kind of source control).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-27-2023 12:48 AM
I am also facing this issue.Any solution you found?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-27-2023 04:38 AM
Upon checking further I see this is a known defect identified from Utah patch 6 and the fixed in Utah patch 8 or Vancouver patch 3 . There is also a workaround for the same mentioned in the below KB article :
https://support.servicenow.com/kb_knowledge.do?sys_id=4be92e4a4702b154b6d8aa25126d4312
If you have a planned upgrade soon then recommend to take the upgrade to fix the Issue, applying the workaround at this point would need you to undo the workaround again before upgrading .
I have attached the PRB1698257 for your reference and the Known error article can be reviewed for further details .
Thank you