Create a queue and its stages

Set up a queue, define its stages and their rules, and choose what happens when an item arrives.

You will create a queue with stages, and learn what each stage setting does.

Before you start: you need Full control on Work queues (the Roles page). To attach the queue to records, create the record type first. To run code when items arrive, create the function first. See Functions.

Steps

  1. Open Work Queues.
  2. Click New queue. To start from a ready-made pipeline instead, click From a template (see Queue templates).
  3. Enter a Name, for example "Inbound dock".
  4. Check the Key. It is made from the name. It allows lowercase letters, digits, dashes and underscores (1 to 60 characters). Permissions and reports use it. It cannot be changed after the queue is created.
  5. Choose an Object type:
    • Standalone (no records) — items are plain codes, like barcodes.
    • A record type — items can link to records, and you can use an intake rule and record updates.
  6. Leave Enabled on. An off queue shows a Paused badge.
  7. Set up the stages. The queue starts with Expected (start), Received and Done (terminal). New queue dialog with the default Expected, Received and Done stages
  8. Optional: open Intake rule — auto-add matching records (see Intake rules) and Settings.
  9. Click Create queue. The queue opens on its board.

Work with stages

Under Stages, the buttons across the top pick which stage you are editing.

  • + Add stage adds another. A queue can have up to 40.
  • The left and right arrows (Move stage earlier / Move stage later) change the order. Order matters: scanning moves an item to the next stage in this order.
  • Remove stage deletes the one you are editing. It is shown when there is more than one stage.

Stage settings

Setting What it does
Label The name people see.
Key Its internal name (lowercase letters, digits, dashes, underscores). It follows the label until you edit it. Keep it stable once items use it.
Kind Start is where loaded and intake items land. Normal is an ordinary step. Terminal closes the item when it arrives.
WIP limit The most open items allowed in this stage at once. 0 means no limit. Moves into a full stage are refused. Loading a manifest is never limited.
SLA seconds How long an item may stay before it counts as Overdue. 0 means no limit. The clock starts when the item enters the stage.
Accept from Which stages may send items here. Empty means any stage.
Write onto the linked record when an item enters this stage Only for queues with a record type. Add record update sets a field on the item's record to a value. true, false and numbers are understood.
Run a function when an item lands here Runs a function in the background when an item arrives. See below.
Action buttons Buttons on the board for this stage. Each has a Button label and a function. Up to 10 per stage.
Auto-assign Who gets each item that enters this stage. See Auto-assign.

Stage settings including WIP limit, SLA, on-arrival function and action buttons

Details:

  • Terminal stages mark an item done and free its key, so the same code can be loaded again later.
  • If a move is refused you see a sentence such as "'Received' does not accept items from 'Expected'" or "'Packing' is at its limit of 5".
  • A record update runs first, with the permissions of the person moving the item. If it fails, the move does not happen, so the record and the queue never disagree.
  • The on-arrival function runs as the person who moved the item. A failure is logged and does not undo the move. It is the only automation a barcode-only queue can have.
  • An action button runs its function once for each item you pick, up to 25 at a time. You need permission to move items and Can run on Custom code. The result shows as "Ran on N items", or "k/N ok" with the first error.

Auto-assign

Under Auto-assign, set Assign each item that enters this stage:

  • Nobody — leave it unassigned (the default).
  • Take turns — round robin through the people listed, then the role's members.
  • Whoever has the fewest open items — the person with the fewest open items assigned in this queue; a tie goes to whoever is listed first.

Then choose People, Or everyone in a role, or both.

  • It applies to new items added straight into the stage without an assignee, and to every item moved into the stage, which gets a new assignee.
  • A person picked by hand when the item was added is kept.
  • People who are suspended, or who can no longer move items in this queue, are skipped. If nobody is left, the item stays as it was.
  • The new assignee gets the usual "Assigned to you" alert, and the item's activity shows Assigned by rule.

Settings

Setting What it does
Unknown scan Reject it reports a scanned code that is not in the queue. Use this to check deliveries against a list. Create an item accepts it as new work, for open intake.
Lease seconds How long a claim holds an item before it is free again. 0 to 86400. The default is 300.
Allow duplicate keys Lets two open items share a key. Off by default, which makes loading and scanning safe to repeat.

Alerts

Open Alerts in the queue's settings to decide who is told about what:

Setting What it does
Tell people when work is assigned to them On by default. When someone assigns an item to another person — one at a time or in bulk — that person is told. Picking up an item yourself (claiming it) never alerts.
Due-soon warning (minutes) Warns whoever holds an item this many minutes before its stage SLA seconds run out. The default is 60. 0 turns it off.
Alert when an item is overdue On by default. Whoever holds an overdue item is told once.
Overdue work nobody holds goes to Shown when overdue alerts are on. People to tell about overdue items nobody is assigned to or holds. Empty means the queue's creator.

Alerts arrive in the inbox and open the item. Each person also gets at most one email every 15 minutes, following their own notification settings. Each item alerts once per deadline: moving it into a stage with a fresh SLA starts a new one. Due-soon and overdue checks run every few minutes, and only people who can still see the queue are told.

Edit or delete a queue

  • From the queue's page click Edit, or use Edit on the card's right-click menu in Queues. Change anything except the key.
  • Duplicate on the card's menu opens a copy of the queue's stages and settings as a new queue.
  • You cannot remove a stage that still holds items. You see "stage '' still holds N open item(s) — move them first".
  • Delete on the card's menu asks you to confirm Move to trash. The queue, its items and their history go to the trash, and the message has Undo. You can restore it from Settings › Trash for 30 days. See Trash.
  • The right-click menu on a card also has Open, Open in new tab and Copy key (for functions).

Stage deadlines can count only working hours, and late items can alert, reassign or move on their own. See Business hours, paused clocks and escalation.

Tips

  • For a delivery check, keep the defaults: load the list into Expected, scan into Received, and finish in Done. Leave Unknown scan on Reject it or choose Create an item to catch extra items.
  • Use SLA seconds for deadlines: 3600 is one hour. Pair it with Alerts so the holder hears before it runs out.
  • A workspace can have up to 200 queues.

Troubleshooting

use lowercase letters, digits, - or _ (1-60 chars) Fix the Key.

a queue with that key already exists Pick a different key.

Give the queue a name. / A queue needs at least one stage. / Every stage needs a label. Fill them in and try again.