Task prioritization
under review
T
Tim Mackey
For the most part, it doesn't matter if Mechanic's tasks are somewhat delayed sometimes. However, when building tasks that directly interact with the shop's storefront, it becomes much more important that the task run as soon as possible, if not immediately.
Taking into account good practices of letting the customer know that they need to wait for the task to complete, it would also be helpful if there was a way to prioritize tasks like this. Tasks with prioritization would be pushed to the top of the task queue (after any other prioritized tasks), allowing less time-sensitive tasks to run afterwards.
The level of granularity to this prioritization is up to debate, but it should probably be kept simple so as not to get confusing or hard to manage.
Teara McGinn
Isaac Bowen in my work with clients I have come across 2 main groups of situations -- 1 being where I know a task is a beast, and I'd like to set it to run in the background (low priority). And the other situation being where a task is really time sensitive (customer facing or related to rush fulfillment) and I need it to run right away even if there's other stuff in the queue (top priority).
If there was the option to set a task as "top priority", then one could create the situation of a background task simply by making all other tasks "top priority", so long as the top priorities still run in a FIFO basis (rather than the new tops always take precedence over the old tops haha).
Isaac Bowen
Teara McGinn: wow, loving loving loving the solution design flexibility you're bringing here. thank you. :)
Isaac Bowen
Chiming in to say that I'm paying attention to this thread. I love the idea of solving this really, really well for y'all, and that's where I intend to go.
Keep adding context, please - the more use-cases the better.
Teara McGinn
Just had another client convo about this feature -- really would love the opportunity to set a task as "background" -- meaning, only run when nothing else is going on
L
Lillian
We urgently need this feature too! Sometimes we have 10+ tasks for an order and it takes quite a while to run, but some features need to happen immediately (e.g. warehouse integrations, etc...) so would love to have this ability.
Brad H (Tekhaus)
Or how about letting a concurrent queue be designated as only running for certain event types?
For example, letting new orders get through when the queue is jammed full with 50k product updates.
Teara McGinn
Having this feature would really make customer-facing tasks feel less risky! Upvoted!
M
Magnus Kromann
This is would a lovely feature :-)
Brad H (Tekhaus)
Piggy backing on this topic. Maybe also include the ability to assign a "max_concurrent_runs" setting to a task.
As an example, a tagging task that needs to update 300k customers will take a long time to run, tying up all of the runs until it is done unless there is some delays built into (via a custom event). If instead that task could be directed to only ever use the shop's concurrent run limit minus one, then all the other tasks could get some bandwidth.
Matt Sodomsky
under review