Flow Designer - Erro - Invalid pharmacy compound uuid: 4e536ea7-84ba-4819-bedb-344306fef337

[Bruno Moreira]

  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

[Bruno Moreira · Accepted solution]

I removed the "Get catalog variables" component and inserted it again and the problem was solved

[phil_bool_unifi]

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!

[ChikeA_]

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.

[newmanan]

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.

[Blessing3]

I had the same issue and I was very close to re-creating the entire flow but thankfully I found the issue after going through each Line action in the flow. The issue was due to a wrong entry in two of my data pill. See screenshot for an example of what was causing the issue. 

Once I deleted that entry and fixed the data pill, it worked. 

 

[Edxavier Robert]

Please look at this KB from ServiceNow

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1710698

As @Blessing3 mention this is due a data pill issue. Please go into each of your steps and verify one by one.