Hi,
We are experiencing an issue with two execution packages, 2_A and 1_B, which are configured not to run concurrently (they are not marked for concurrent execution in the Execution Package Editor).
However, we have observed that they are running at the same time.
Here is our setup:
-
2_A is part of a chain and runs as a post-execution step after 1_A.
-
1_A is allowed to run concurrently with 1_B.
-
Since 1_A typically completes much faster than 1_B, this sometimes results in 2_A starting while 1_B is still running.
We want to prevent 2_A and 1_B from ever running simultaneously.
Could you please clarify how concurrency is evaluated in this scenario?
Is it determined by the parent package (1_A) settings, or should the restriction between 2_A and 1_B be enforced differently?
What would be the recommended way to configure this to ensure 2_A never starts while 1_B is still executing?
