The maintenance loop has paused discretionary work because it is over the spend budget set for it.
You do not need to do anything. The loop starts again by itself when the budget allows.
To start it sooner, comment here with the word override budget and what you want done:
override budget: finish the renewal flow on #289
That releases the budget for that one instruction. When the work is reported done, the loop goes back under the budget on its own.
It releases the budget only. If the model provider is separately refusing requests, the loop waits for that to clear either way.
This issue closes itself when the hold clears.
When you're done: close this issue. The engine re-checks, and if the gap is still there it re-opens this issue once, saying what's missing.
If you don't want this: comment dismiss here — the engine won't ask again for this version. (Commenting done works too, same as closing.)
The done budget-override / dismiss budget-override commands on the liveapp: controls panel still work as well.
The maintenance loop has paused discretionary work because it is over the spend budget set for it.
You do not need to do anything. The loop starts again by itself when the budget allows.
To start it sooner, comment here with the word
override budgetand what you want done:That releases the budget for that one instruction. When the work is reported done, the loop goes back under the budget on its own.
It releases the budget only. If the model provider is separately refusing requests, the loop waits for that to clear either way.
This issue closes itself when the hold clears.
When you're done: close this issue. The engine re-checks, and if the gap is still there it re-opens this issue once, saying what's missing.
If you don't want this: comment
dismisshere — the engine won't ask again for this version. (Commentingdoneworks too, same as closing.)The
done budget-override/dismiss budget-overridecommands on theliveapp: controlspanel still work as well.