Thanks for your response. So I just tried to set up a very simple case of what I am experiencing but of course that worked and my much more complicated case doesn’t. I would have to play around a bunch (which I will get to) in order to make a relatively easily replicatable workflow. My guess is, without that, you’re not going to be able to help me but I’ll generally describe what is creating the issue:
Let’s say I have a db called fruit:
Action 1: Make changes to a fruit: first item. Thing to change: colour = green
Action 2: Show a group only when do a search for fruit (constraint colour = green): count >0
Basically the idea is that, action 2 theoretically won’t show the group if it tries to run before action 1 has finished.
This is the simple example I tried to set up, which works (I was hoping it didn’t for the purpose of this thread). My complicated workflow has a bunch of actions that show and hide groups, a lot of which have “only when” constraints which rely on an earlier action completing.
The other thing I’ll add is that within these complex workflows, there are stripe.js actions which could be part of the problem but I’m not sure they are given that there are actions to show groups that don’t show even though their criteria don’t rely on any of the stripe actions completing.
I’m sure you’re answer is going to be “sorry, I can’t really help you without a replicatable example”. I will try in the next couple of days to create one and post it back here but maybe you have some other thoughts.
Thanks for your help.