Unsupported flowLogic type: TOP_LEVEL_CATCH
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
4 weeks ago
Dear all,
I am on glide-yokohama-12-18-2024__patch7-08-14-2025.
I created a new flow in flow designer with many actions like "Create catalog task", if-conditions, run-parallel etc.
I always clicked "save" and "Activate" after some working steps.
But now - after clicking "Activate" I receive the error "Unsupported flowLogic type: TOP_LEVEL_CATCH".
(see screenshot)
So I used the "Undo" button to go back a few steps and clicked "Activate" again.
But the error remains.
I tried to remove several actions and clicked "Activate" again, but the error remains.
Does anyone know where to get more information about this error or even how to fix this?
Many thanks
Best regards
Eckhard
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
4 weeks ago
Seems something is mis configured with Try flow logic
are you using subflow within your main flow?
check this
How to avoid unnoticed failed Flows
If my response helped please mark it correct and close the thread so that it benefits future readers.
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
4 weeks ago
Hope you are doing good.
Did my reply answer your question?
If my response helped please mark it correct and close the thread so that it benefits future readers.
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
4 weeks ago
Dear Ankur,
the thing is, I did not insert a "try and catch" block.
But I was able to fix this with a stupid workaround.
I deleted my last action, which was a normal catalog task and then when I try to save --> at the top of the flow I suddenly see a "try catch" block, that I deleted then.
But this "try and catch" block was not there before.
One of my colleagues faced the same issue and gave me a hint.
Very strange behaviour and very bad that you can not see any additional information.
