Hmm, yes, that's unfortunate.

In mutex-world, a self-rescheduling job would be far better for responsiveness and would be straightforward. It'll require better coordination/status reporting to the frontend than I've currently implemented, but my current pass does a horrible job of that anyway, so would be worth the fixups.

Let me know if you've come up with any alternate solution, otherwise a rescheduling job makes sense to me.