Receive and manage Queue work

A Queue holds work awaiting or undergoing execution. Pool membership lets a Worker participate under the Queue’s rules; it does not make them a dispatcher or configurator. Already assigned work remains associated with its Queue.

Receive work

Mode	What the Worker does
Any	Select an eligible task and use Take, or Take and start when available.
First / Last	Acquire the current eligible task at the configured end of the Queue order. Personal sorting and filters do not select a different candidate.
Assignment on request	Use Give me work. The Queue evaluates a request for the current Worker without exposing its whole backlog.
Auto-assignment	Receive assignments from enabled background causes, or use Give me work to request one task now.

In both algorithm modes, an authorized dispatcher can use Distribute tasks now for a Queue evaluation. A Worker request targets only that Worker and at most one new task; already assigned work does not replace the request.

Requests can take time. The request dialog can be closed while processing continues. Rechecking the same request does not allocate another task; a later new request is a new intention. A No work result is a normal outcome, not proof that a Queue is broken. An assignment does not automatically Start work.

Availability, active Worker/user linkage, Queue membership, Definition rules, capacity and the Queue’s Work Schedule policy are checked when applicable. Restricted Queues may hide other Workers’ assignments or future candidates. This is a permission boundary: a personal filter or sort cannot reveal them. In First/Last, a filter that hides the eligible end task does not let you take its successor. Personal columns and order affect your view only.

Dispatch and return

A permitted dispatcher or Task administrator can assign or change an Executor. Changing or removing an existing Executor requires a reason. Running, paused or postponed work returns to Idle; a blocked task keeps its block. Nothing starts for the replacement Worker automatically.

An Executor can return work only when the Queue allows returns with a reason. Otherwise a dispatcher or administrator must release it. Returning retains its Queue residence and ordering position; this is not a direct handoff to a peer.

The Queue overview exposes authorized operational load. Limits can prevent an increase in assigned or executing work. Warnings draw attention without becoming intake limits. Where explicitly configured, a dispatcher exception requires a reason and is recorded; it is not a general bypass.

Change order, Queue or availability

Shared reordering changes operational order, unlike a personal grid sort. Routing → Change queue checks current rights, the destination’s admissions and state, and the task’s assignment and execution restrictions. An Executor must be removed explicitly when required; transfer does not remove one for you.

Available from controls when Idle, unassigned Queue work may be acquired or assigned. Reaching that time permits evaluation but does not itself Start work. Availability, Due and Postponed are separate concepts.

Finish operating a Queue

1. An authorized configurator chooses Drain for the Queue.
2. Draining rejects new intake and incoming transfers while permitting lawful processing and outflow of retained work.
3. Complete or move the retained tasks. If configured progress time expires without a reduction in retained work, a stalled-draining signal appears. Editing priority or an assignment does not count as that progress.
4. Deactivate the Queue when its retained work is empty. An attempt to deactivate a nonempty Queue is rejected.

Use signals and notifications to inspect current problems. A full positive capacity limit, future availability or one No work response alone does not mean the Queue is unserviceable.

For setup, use Queues and Workers. For a missing action, No work result or stale request, use Tasks troubleshooting.