Lower a limit while actions are pending
Reduce an agent allowance without mistaking existing reservations or unknown exposure for cancellable work.
Lowering a shared allowance does not undo operations already dispatched. It also does not erase reservations or unknown exposure. Treat the change as a control on further applicable work, while you separately inspect what is already in progress.
Anlyon's limit reference states that lowering a limit never releases existing exposure. New work is blocked until availability recovers. Archiving a limit stops it applying to new effects while its existing reservations still settle. Those are materially different administrative actions.
Inspect before changing
Record the environment, limit identifier, scope, current amount, consumed quantity, reservations and unknown exposure. Identify which agents and actions use it. If the reason for the change is an active incident, consider the environment halt separately; reducing one limit is not a substitute for stopping all new dispatch in that environment.
Suppose a limit is 100 units, with 80 already committed, and an operator lowers it to 50. Do not expect 30 units of previous work to disappear. Inspect the authoritative availability and rejection reasons after the change.
Choose the intended action
| Operator intent | Relevant action |
|---|---|
| Reduce future exposure | Lower the applicable limit |
| Stop new environment dispatch | Use the environment halt |
| Remove this limit for future work | Archive it, after checking the consequence |
| Establish what a timed-out action did | Reconcile or resolve that effect |
Keep these decisions in the change record. Archiving a restrictive limit to make a dashboard warning disappear can permit more work than intended.
Validate and communicate
Use a safe request that would exceed the new available capacity and confirm it is refused for the expected reason. Check another intended scope to ensure the change was not applied to the wrong environment. Tell operators which existing operations still require attention.
Only credentials authorized to change limits should perform this procedure. Do not hand those privileges to the constrained agent as a recovery mechanism.
Follow impact-limit semantics, incident recovery and manual outcome resolution for the separate decisions involved.