Join the #BuildWithBuildAgent Challenge! Get recognized, earn exclusive swag, and inspire the ServiceNow Community with what you can build using Build Agent.  Join the Challenge.

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

Bruno Moreira
Tera Expert

 

  has anyone experienced this error when activating a Flow in the Flow designer?

 

BrunoMoreira_0-1721918324316.png

 

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

2 ACCEPTED SOLUTIONS

Bruno Moreira
Tera Expert

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

View solution in original post

Paul Sisson
Tera Expert

*** UPDATE ***

There is a solution that has not been accepted as the "official solution" but it definitely is the best one.

 

The problem:

You have a data pill somewhere that is broken/corrupted/mapped incorrectly.

This is typically due to removing an input that was previously used or needed, but I'm sure it happens other ways.

 

The solution:

Go find the data pill that's corrupted and fix it. You might have to go through each input on each step to find it, and there might be more than one.

 

SHOUT OUT TO @JeevesS  for the solution. Go give him/her a thumbs up!

 

*** END UPDATE ***

 

I didn't have a "Get Catalog Variables" action to delete, so I just deleted everything and re-did it. Worked like a charm!

View solution in original post

25 REPLIES 25

Kelly Logan
Kilo Sage

It really seems like sometimes a reference of some type gets corrupted, but it's not clear what it is. It would be very helpful if we could translate these into a specific object or connection to look at and diagnose. So far the only solutions seems to be 'delete everything until it starts working'. 

danielanork
Tera Contributor

I also had this error and think i found a good way to troubleshoot and resolve it.

"Invalid pharmacy compound UUID:" refers to the table sys_hub_pill_compound, where the field "UI Unique ID" is the sys_id being referenced in the error.

Steps to Troubleshoot:

  1. Navigate to: sys_hub_pill_compound.list
  2. Filter by:
    UI Unique ID = [enter the sys_id from the error message
  3. This will return a list of pill compounds.
    In the "Pill Prescription" column, you'll see the sys_id and the name of the data pill.
    Go through your flow and remove any references to this data pill.
  4. Try activating your flow again.


This issue seems to happen when a copied flow tries to reference a data pill from the original flow. Since the reference is no longer valid in the new context, it throws the error. 

Bless you for this contribution. I've been aware of this issue that pops up with corrupt data pills in Flow designer for a while. The idea of having to search out / find the one that's broken and/or clear every single one of them makes me want to pull out my hair.

This method was the fastest way I've seen to find the exact data pill(s) that I needed to remove.

ViktoriaMikoova
Tera Contributor

I have run into the same issue, removing and replacing the Get Catalog variables action didn't help. It's a shame I didn't noticed solutions from @danielanork Blessing3 and newmanan as they would have saved me a lot of time and I think they should be the accepted solutions. 

Anyway, how I found the exact step that had the corrupted data pill instead of going through every step was this: 

I opened the System Diagnostics -> Session Debug -> Debug Log and then run test on the flow again. 
In the logs I got the "Invalida pharmacy compound uuid" error again but before it you can actually see which step was the last that was created OK - in my case step 20 so then it was easy to go to step 21 and find the corrupted pill there. By replacing the corrupted data pill the issue was fixed.

ViktoriaMikoova_0-1752743890483.png

ViktoriaMikoova_1-1752743924736.png

 




Viswa2
Tera Expert

I removed and disabled the "Error Handler" within sub flow, which resolved the issue. Added back "Error Handler", I was able to save and publish the sub flow successfully.