Hey. I have a long backend workflow that needs to finish ASAP.
During that workflow, I want to publish status of this workflow into the “status” thing.
My question is - is it faster to make changes to status in that workflow or to call another API workflow and do the change in there in parallel.
So essentially the question is - what operation is faster - schedule API workflow or make changes to thing?
I don’t care about how fast I can update the status, I just need the main workflow to be finished ASAP.
I know this is super advanced but your answer will help a ton.
This isn’t a simple question, as it depends on the complexity of the change you want to make.
Sometimes, depending on the connection speed and CPU power of your user, it’s faster to just throw it at the Bubble server for processing. If it’s just a status change, it’s probably faster to do it during the main workflow…
It will be triggered from backend workflow, so user CPU is completely irrelevant
Sorry…
I misunderstood your problem…
I thought that the main workflow will be running in front end.
In this case, things change 
It should be faster to keep the action in the main workflow in the very first step…
1 Like
Agreed. If it’s a simple operation like updating a status, the difference should be negligible. If it was another long workflow you wanted to run in parallel, that would be a different story.
1 Like
