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
{{ message }}
This repository was archived by the owner on Dec 23, 2021. It is now read-only.
Getting around this issue at the minute by setting interval to around 10 minutes. The system timer used only fires elapsed after first interval so if this was set to 45minutes for example, all workers would be dormant for this length of time.
It would be great if there was an option for 1st worker to attempt a lease as soon as deployed and then all workers to complete on next interval. Commonly we deploy to an Azure region one at a time and therefore all workers would not have a new version at the same time.
We don't use priorities at the minute, which are all set to zero, and realise this may be a complication for applications that do use.