...
The actions run in their normal order but each flow in their own queue, the last queue waits until the first one is done before running. Making the process serial
All actions are visible for both records because the shared queueable group. This causes the two to have a dependancy
Upon an error all consecutive actions inside a queue are skipped
NOTE: Beware of the “Maximum stack depth has been reached.“ error. See considerations above.
Scenario 008: Two DMLs in a separate transaction for record A
The actions run in their normal order but each flow in their own queue, causing the two to run parallelthe last queue waits until the first one is done before running. Making the process serial
The actions are only visible for record A due to no dependency, both transactions are shown
Upon an error all consecutive actions inside a queue are skipped
NOTE: Beware of the “Maximum stack depth has been reached.“ error. See considerations above.