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
We could add a new (optional) priority field for POST /pipelines/schedule and order the queued job according to that priority. If you need to always get to the top of the queue, you could e.g. use a timestamp for the priority.
We have two kinds of jobs. One that should be prioritised and the others go to the end of the queue. So if I provide a timestamp and if it's not null it should go to the top, that would work for me 🙂
We have the requirement to schedule certain jobs at the top of the queue depending on some parameter.
Is this already possible with one of the existing strategies or does this need some new implementation?
The text was updated successfully, but these errors were encountered: