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

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

21 REPLIES 21

Just to re-emphasize or maybe clarify, I had to delete the entire Flow and recreate it..BUT..I just opened the Flow to be deleted on one tab and a new Flow on another and copied exactly what I did before. Works fine now.

Bruno Moreira
Tera Expert

terrieb

 

Can you test your flow? I found that the error was linked to my "Get Catalog Variables" in the test message. Try to do a test even with the unpublished flow and see what the error message is.

 

 

Now I get this message - flow won't test.  

Could not retrieve snapshot for test using snapshotId : fe669da41be412d04dd4ece66e4bcbf7

 

Sigh....

I went back to the original one, made the changes I did to the copied one, and then activated the original and got no error messages this time... crazy

 

Testing it now.  Fingers crossed it works now

Community Alums
Not applicable

Removing the 'Get Catalog Variables' step would have major consequences - every field using these variables would need to be rebuilt. This should only be considered as a last resort.

 

The problem is likely caused by a single corrupted step. Here's how I solved this issue previously:

  1. Clone the entire flow
  2. In the cloned version, delete one step at a time (starting with recent changes)
  3. Try saving after each deletion
  4. When the save succeeds, you've identified the problematic step
  5. Return to your original flow and recreate only that specific step

This method helped me identify and fix the corrupted step while preserving the rest of the flow.