Flow Designer visibility failure
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-04-2024 08:51 PM - edited 03-04-2024 09:13 PM
Hello guys.
After upgrading our instance from the Tokyo version to Vancouver, we noticed an impact on the Flow Designer visualization:
In summary, after executing the flow successfully, Servicenow changes the name of the subflow to "payload" (I don't understand where this name comes from, as the subflow has a completely different name) and it is not possible to view its details, the subflow is stuck and the actions that were performed do not appear.
I added 3 evidence that explain the problem.
Thanks a lot for the help,
Best Regards,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-04-2024 09:31 PM
We tried to recompile the subflow as well, and this error message appeared, even referring to this "payload"