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
When you change schedule on your cron container, instead of assigning it for the first time, it gets picked up, but because uuid does not change (i thought it would!), it does not update the schedule at which it runs in the cron service.
Steps to reproduce
Assuming cron is running (in debug mode) and has registered a scheduled container
Go to service with scheduled container and change the schedule to be more or less frequent
See that new schedule is displayed, but not reflected in the schedule that actually runs
What should happen
Cron service should pick up new schedule, check to see if its the same as old, if not, mark the current cron job as "stale" and add a new one for new schedule
Workaround
Restart cron service.
The text was updated successfully, but these errors were encountered:
Description
When you change schedule on your cron container, instead of assigning it for the first time, it gets picked up, but because uuid does not change (i thought it would!), it does not update the schedule at which it runs in the cron service.
Steps to reproduce
What should happen
Cron service should pick up new schedule, check to see if its the same as old, if not, mark the current cron job as "stale" and add a new one for new schedule
Workaround
Restart cron service.
The text was updated successfully, but these errors were encountered: