
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-25-2024 07:40 AM
has anyone experienced this error when activating a Flow in the Flow designer?
I can change and save my flow. I can test the flow, but I can't activate my flow.
I'm on the Washington DC version patch4-hotfix1
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-25-2024 12:12 PM
I removed the "Get catalog variables" component and inserted it again and the problem was solved
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-30-2024 12:58 PM
I didn't have a "Get Catalog Variables" action to delete, so I just deleted everything and re-did it. Worked like a charm!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-29-2024 01:33 AM
Yeah, I've had this issue today on a copy of a Flow - I wish I'd googled it earlier, it was such a specific error I presumed another flow in our instance was causing it! Thanks, all, for sharing this. I'm going to clone this copy and hack out rows until I find out which one is broken. It's a big flow (integration). Wish me luck!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-14-2025 10:33 PM
@Bruno Moreira I am facing this issue tried all things which you mentioned but no luck.
You have any update on this how to tackle this issue?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-24-2025 05:58 AM
So the issue is occurring because at least one line of the flow is 'corrupted'.
Your best approach would be to create a copy of the flow, then work upwards from the bottom, deleting rows and re-trying to publish until you stop getting the error.
Make a note of the line that enables you to save the flow.
Then make a new copy of the flow, and in that copy, only change that one line. If it's exactly right, delete it, save it, and re-add the same row. See if that solves it. If it doesn't, a second line is also corrupt. Repeat the process, but starting from the line you've already changed.
Sorry there's no better solution than this. If the flow hasn't got much content, just recreating it from scratch may well be quicker. It can be exactly the same - the issue isn't that the flow is wrong, just that the record that stores the flow and runs it isn't aligned with the flow as you're seeing it. That's become corrupted.
Hope that helps!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-22-2025 09:05 AM
Just ran into this issue. The UUID listed was part of a corrupted data pill in one of the Flow's steps, labeled "fd_transform:{UUID Here}". Can't say what caused it, but replacing the data pill did the trick.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-20-2025 06:23 AM - edited 02-20-2025 06:24 AM
Thanks to the above for their experiences.
Rather than deleting anything.... for me, the solution to this was to simply look through each of my flow action steps until I found one where the data pill value looked corrupted. It was an If action, and the condition looked like {{fd_transform:UUID...etc. So, I cleared that out and set it again. Saved it. Then I was able to Activate the flow successfully.