Recently, we have been working on a new cronjob execution predicting and tracking system to make sure that it won't miss any cron execution, and can automatically resume the service even after a service glitch or downtime. If it's done correctly, it'll greatly increase the service reliability and usability, as you can also see when your cronjob will execute with its current time settings.
Unfortunately, I have deployed it prematurely without proper system update, and it caused multiple executions (because of the auto retry feature) and missing executions from May 24, 21:25 to May 25, 00:44 UTC time.
I have rolled back the update and everything works normally like before.
I'll double check the update and make sure to deploy it carefully step by step to make sure this won't happen again.
UPDATED: The bug was found and fixed and the update is released.
I'm really sorry for the inconvenience it caused. As a token of our apology, I have added a credit of 10% of your account plan price (e.g. $5 for Platinum accounts) to your account balance.
We also have more update and upgrade in the coming time, and we'll let you know via this blog.
If you encounter any problem with SetCronJob, please us know ASAP.