You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the status of a task is error, this task runs every time when the OS cron job runs even it's not the scheduled time.
For example, we set the task scheduled time to */5 8-20 * * *, if it's error, it will be run even after 8pm until the task runs successfully.
Below snapshot shows the scenario:
The text was updated successfully, but these errors were encountered:
@tsun424 this is expected behaviour AFAIK, so if for eg an API is down it will retry until it succeeds. However there should probably be an option here, eg $automatic_retry_on_fail = true
The mechanism of retry is OK, but I think this retry should happen only during scheduled time. From my point of view, scheduled time should have higher priority in this scenario. If a new option will be added, how about $automatic_retry_out_schedule?
it really depends on the job. because you say it should only happen during the scheduled time.
That works find if you have * 10-16 * * * but not if you have 0 0 * * *
Might make more sense to have a $retry_schedule option with the same format, default being * * * * *
If the status of a task is
error
, this task runs every time when the OS cron job runs even it's not the scheduled time.For example, we set the task scheduled time to
*/5 8-20 * * *
, if it's error, it will be run even after 8pm until the task runs successfully.Below snapshot shows the scenario:
The text was updated successfully, but these errors were encountered: