Skip to main content
Question

Concurrent execution packages in package chains

  • August 24, 2026
  • 4 replies
  • 47 views

Hi,

I have two Execution Package chains ("Run Packages...") configured as follows:

Chain 1:

  • 1a) Revenue
  • 1b) Revenue Trigger
  • 1c) Morning
  • 1d) Morning Trigger

Chain 2:

  • 2a) Store
  • 2b) Store Trigger

The requirement is that 2a) Store and 2b) Store Trigger must not run concurrently with 1c) Morning or 1d) Morning Trigger.

I have configured this restriction in the Concurrent Packages section under Edit Execution Package. However, the restriction does not currently seem to be enforced as expected.

Could this be because 1a) Revenue and 1b) Revenue Trigger are allowed to run concurrently with 2a) Store and 2b) Store Trigger?

In other words, when Execution Packages are part of a chain, do the concurrency restrictions need to be configured for every package in the chain? Or should the restriction between 1c/1d and 2a/2b be sufficient to prevent those specific packages from running at the same time?

4 replies

Thomas Lind
Community Manager
Forum|alt.badge.img+5
  • Community Manager
  • September 2, 2026

Hi ​@annfoss 

Do you start these runs with a Orchestration process?


Christian Hauggaard
Community Manager
Forum|alt.badge.img+5

Hi ​@annfoss 

Which version of timextender are you using? Do you have an update on Thomas’ question above?

Thanks


  • Author
  • Participant
  • September 21, 2026

I am using 20.10.74.64. TimeXtender Classic. 


Thomas Lind
Community Manager
Forum|alt.badge.img+5
  • Community Manager
  • September 22, 2026

Hi ​@annfoss

Thanks for the update. I would say yes it is because 1a is allowed to run at the same time as 2a.

I assume you use run on success in the packages to go from 1b to 1c.

Perhaps using a major package with the others as sub packages in them, will make it work better.

Outside of those named morning, what sort of schedule does the various parts run on, once a day or multiple times?