Hi,
Are there any plans to fix this bug?
Could this have been avoided by using Cron.Hourly rather than explicitly specifying a cron expression?
What can we do to prevent this from happening in the future?
Hi,
Are there any plans to fix this bug?
Could this have been avoided by using Cron.Hourly rather than explicitly specifying a cron expression?
What can we do to prevent this from happening in the future?