Do not consider a job as misfire when it is resumed after the server was in stand by mode

[pablovb]

When the server is in standby (after calling standby()), if you create new jobs with triggers during that mode, when you "wake up" scheduler by calling scheduler.start(), all triggers that should have been executed during that period appear as misfired.

There should be an option (properties or method) to avoid these misfires.

A tipical use case is to:

• Start the server in standby mode (start() + standBy())
• Create/Import scheduled jobs
  • You do not want them to be executed until all jobs are created
• Resume Scheduler (start())
• From this moment, apply scheduling.

Thanks.

[jhouserizer]

The typical way people do this is to set the start time into the future; but this could be considered as an enhancement feature.

[pablovb]

Hi Jhouserizer,

Yes, that could be a workaround as long as the feature is not implemented. It's still not perfect, because the future start time would have to be an arbitrary time (you don't know how long the import process will take), so it could be too long or the opposite.

Regards.