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

24 REPLIES 24

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.

phil_bool_unifi
Tera Guru
Tera Guru

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!

samruddhi30
Tera Contributor

@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?