Do backend API workflows wait until they complete before moving to another step?

Questions
21

Aaah okay that’s an interesting hack! I think I now understand why so many templates come with a “hidden variables” element with a bunch of other hidden elements in them! Lol

I’m having most of my issues with backend workflows though so still need to figure that out. For the time-being I either have tons of duplicated spaghetti or jump into private plugin code (neither of which truly solves the underlying issues but alas).

22

For backend workflows (and front, for that matter) the best strategy I’ve found so far is to daisy-chain things. So you do a workflow which calculates whatever you need, then pass to the second workflow, which passes to the third, etc. Using my example from above:

A = API_Request();
B = A * Another_API_Request();
C = A + B;
D = C * tax_rate;
E = C * B * A / D;

I’d do it this way:

Workflow A

  • Call Workflow B and pass A (API_Request():wink: and tax_rate as a params.

Workflow B

  • Call Workflow C and pass A, B and tax_rate as params.

Workflow C

  • Call Workflow D and pass A, B, C and tax_rate as params.

Workflow D

  • Call Workflow E and pass A, B, C and D as params.
23

I stumbled upon this forum question when looking for an answer to another question I have about recursive workflows.

Thought I’d add this more recent video that officially clarifies a few things that are discussed in this thread:

It might help someone in future.