Help

Help›Commitments›Release the chase

Release the chase

Reviewed Sep 7, 2026

View as Markdown
Words
TierPro

The question this page answers ​

Which style has won, how much of the reserve goes to chasing it, and what does the release leave held?

What you see ​

Release the chase spends the chase reserve on a named winner: the act the reserve was declared for. The head names the commitment. The reserve is a row set of three legs, and it stays three legs at every step: declared, released, still held. What the reserve has paid for lists earlier releases as the record holds them. Choose styles to chase picks one or more winners from the styles inside the commitment's scope, and with one picked, How it is selling reads its evidence per channel beneath the pick. The release is a dollar amount, never a percentage, per style where several are picked, capped at what is still held, with Release all beside it; Why is this changing? asks for a reason code, the note optional.

The consequences before the button say what moves and what does not: the dollars move out of the reserve into open to commit on this scope, where they are not ring-fenced, and what stays held; and the declared reserve does not change, because this spends against it and writes no amendment. The engine's own refusal, where there is one, stands above everything else on the page, verbatim.

What to do ​

Releasing takes the Commitments door, an admin or a member given it. Name the winner, name the dollars, pick the reason, press Release. The receipt renders where the button was, naming the winner, the dollars, what is still held and what was released before, recorded as the next version. There is no way back through this page: a release is a version on the record, and the reserve is refilled only by amending the declaration to hold more back. On Work the buy the Today reading offers this act while a reserve is releasable, and it is under On this commitment. The book's row door and the room's acts offer it too.

When it is empty or failed ​

No commitment at this address.

The declaration did not come back.

The reserve does not exist until the declaration is signed off.

A closed season's reserve closed with it, and the page says so in place of the fields:

This season is closed, and its reserve closed with it.

A seat without the Commitments door reads:

Releasing a buying reserve needs org-admin access.

The fields refuse in place until they are answered:

Select at least one style to chase.

Enter an amount to release.

That is more than the reserve still holds. Release what is there, or amend the reserve to hold more back.

A position that did not answer is a failed read, not a reserve of zero: the head says the reserve is unknown and nothing can be released against it, and Read it again is offered. A catalogue that did not answer lists no styles and says:

Catalogue failed to load. The server refuses, as an answer about the state and never as a bad request, a closed commitment, a channel scope, no declared envelope, no declared reserve, a boxed window past its buy lock, a reserve already fully released, and a release larger than what is still held; the last one carries the declared span, what was released before, and what is still held, so a concurrent release can be told from a mistyped figure. A style outside the scope is refused with the scope it falls outside.