Hi guys,
I have a couple of external APIs that send info to an endpoint in my app.
Yesterday I came across a situation I hadn’t seen.
2 different API calls to my endpoint arrived at the same time. Depending on some of the parameters they carry, a separate listener trigger fires in my backend.
Both listeners fired and they both started their own workflow tasked with updating the same Thing with the info from the payload.
What I’ve detected is that not all the fields they were supposed to update were updated (each has to update around 3 fields in the Thing). Especially if the field to update was the same in both workflows.
I had in my mind that Bubble would, in these extreme circumstances sequentially run these, but it seems that this was not the case. Workflow A started to change Thing in its original state, and then Workflow B instead of picking the Thing in its post-chang state (after Worfklow A was done with it), actually picked it up in the same original state.
So I’m left with a Thing partially updated, which caused some headaches of course.
Questions: Is this the expected behaviour? And if so, do you have any suggestion on how can I force the Thing to be sequentially updated?
Thanks!