Welcome Guest! Log in
Stambia versions 2.x, 3.x, S17, S18, S19 and S20 are reaching End of Support January, 15th, 2024. Please consider upgrading to the supported Semarchy xDI versions. See Global Policy Support and the Semarchy Documentation.

The Stambia User Community is moving to Semarchy! All the applicable resources have already been moved or are currently being moved to their new location. Read more…


The same delivery has two schedules for different periods. Sometimes these periods have conflicting occurences. When this happens, the delivery is executed twice.

For example:

  • Schedule 1: execute delivery1 every tuesday at 10am
  • Schedule 2: execute delivery1 every 5th month day, at 10am

=> When the 5th day of a month is a tuesday, delivery1 will execute twice.


This is normal, considering the default configuration of the Scheduler.

When a scheduled job tries to start, it will wait for the other occurences to finish. If the "misfireThreshold" delay is reached then the awaiting job is cancelled. By default this delay is 60 seconds.

You can change this behavior in file stambiaRuntime/properties/engineScheduler.properties.

  • Create this file if it does not exist (copying engineScheduler.properties.sample)
  • Change this line:
    org.quartz.jobStore.misfireThreshold = 60000
    org.quartz.jobStore.misfireThreshold = 1

=> the awaiting job is immediately cancelled (after 1 millisecond...).



Knowledge Base

Suggest a new Article!