How can I prevent timers start event scheduled with a cron to resume missed events after a scheduled downtime?

Submitted by marielle.spiteri on Wed, 12/09/2020 - 01:04
1
0
-1

Hi,

I have a process that is set on a schedule using "Start Event" with a "Start Timer" using a cron schedule "0 0/5 * 1/1 * ? *" to run the process every 5 minutes of every day.

When I have a scheduled system downtime and the Bonita app server is completely shut down, the process stops, but when the servers start back up, it will immediately fire off events to start the process X number of times depending upon the length of the downtime.

For example, the server is down for 17 minutes, immediately 3 instances of the process are kicked off.

In this case, I only want 1 and for the schedule to resume as per the normally defined timings and not try to make up the missed events.

Can this be done and if so how?

Thank you!

event
Timers
cron
1 answer

Submitted by Pablo Alonso de... on Wed, 12/09/2020 - 15:26
1
+1
-1
This one is the BEST answer!

Hi Marielle,

As it is a planned shutdown, what about disable and enable the process before and after restart? it will deactivate the trigger of the Start Event.
As another option, the process could be adapted to do not be triggered more than once (kind of singleton)

I hope it helps

Comments

Submitted by baptiste.mesta on Wed, 12/09/2020 - 16:16

We don't offer the possibility to configure the misfireInstruction of the quartz trigger.

It might be possible to manually update the database to change that, but it's not a great thing to do.

Since we do not have that possibility out of the box, I would also suggest to have it in the process itself as Pablo said.

i.e. have an automatic task calling the API to verify if there is already an other case of the same process already running and also having something like a check that verify if the last time that process was executed is too recent or not

HTH.

Permalink
Notifications