Beaker 0.17 added support for harness independent system reservations after a recipe is completed or aborted. As these are managed by the server, they could be made configurable via the web UI and bkr CLI for a previously submitted recipe.

The kinds of cases where that feature seems potentially interesting are:

* After manually kicking a recipe that stalled for some reason (the case
that prompted the idea)
* After noticing something odd in the execution of a long running recipe
* Switching from "always" to "only on failure" if you forget to make it
conditional (or vice-versa)
* Adding or removing the reservation request if you simply made a mistake at
submission time

Rather than building this into the current job details page, it is suggested to consider this proposal further after that page has been redesigned (tentatively under consideration for Beaker 20 in early 2015).