Hello good day!
I would like to report about some certain timers that do not run on schedule seldom times in the system. This is very critical since there are other processes that is dependent on these timers and needs to be triggered on specific times. Some of the ex
Here are some of the examples we have gathered on these timer methods specifically:
- Chargebee Sync Timer
- DatabaseAddNextCalendarSessionObject Timer
Here is our App ID: 4A47197B-AE30-FA84-FF56-0071F4010900
Thank you!
Hi Kean,
I looked through the timer definitions and the run history. Here’s what I see:
DatabaseAddNextCalendarSessionObject - this timer has the following cron expression:
0 0/5 9 * * ?
In plain English, this expression translates to the following schedule:
Every 5 minutes, all within the 9:00 AM hour,
in whatever timezone the scheduler is configured to use (US Central timezone)
The detailed explanation is below:
- Seconds: 0 → at second 0
- Minutes: 0/5 → every 5 minutes starting at minute 0 (i.e., 0, 5, 10, … 55)
- Hours: 9 → during the 9th hour (9 AM)
- Day of month: * → every day of the month
- Month: * → every month
- Day of week: ? → “no specific value” (used because you already used day-of-month as *; Quartz wants you to specify one or the other)
So it fires at:
9:00:00, 9:05:00, 9:10:00, …, 9:55:00
every day
In the screenshot you provided, you can see it ran 12 times during the specified hour (shown hours are in UTC):
As for the chargebee_payments timer, I looked through the execution history and did not see any skipped executions. If you can pin point one, please do.
Regards,
Mark