Print queue and "Needs a decision" jobs

Every receipt, register invoice, report or label is a job in the queue. The "Queue" tab shows what is waiting, what has been printed and what needs your decision. The list refreshes itself, and jobs awaiting a decision are always at the top.

Job statuses

• "Queued" (queued): the job is waiting to be fetched by Bridge.
• "Picked up by Bridge" (assigned): Bridge has fetched it and is not printing yet.
• "Printing" (printing): printing is in progress.
• "Printed" (done): the device has confirmed, usually with the document number and amount.
• "Error" (failed): the print failed, and the details contain a message.
• "Needs decision" (needs_decision): the system does not guess and waits for a human.
• "Cancelled": the job was cancelled manually.

Why a job needs a decision

• No rule: no rule matches the document (point, workstation, channel or payment).
• No usable device: a rule matches, but its devices are disabled or will not process this document.
• Unknown result (failed_unknown): Bridge lost connectivity during printing and it could not be determined whether the receipt came out.
• Overdue in the queue: the device from the rule has been unavailable for too long (after approx. ten minutes).

What to do with a "Needs decision" job

1. In the "Queue" click "Show jobs awaiting a decision" and "Resolve" next to the job. In the window, read the reason in the "This job needs your decision" box.
2. If the reason is an unknown result, you will see the box "It is not known whether the document was printed". Check at the register whether the receipt came out, and compare the document counter.
3. If the document did physically come out, click "Mark as printed" (document number and note are optional). The system will not print it a second time.
4. If it did not come out, tick "I checked the device: the document was NOT printed." and choose: "Retry according to rules", "Redirect to selected device" (you pick the device explicitly, with no default) or "Cancel job".
5. If the reason was a missing rule, add it in "Print rules" and retry the job.

Confirmation that it "was not printed" is required when the result is unknown or the job is in progress (fetched or printing). Retrying without checking may print a second receipt, and two receipts mean two sales in the register. Cancelling a receipt leaves the sale without a fiscal printout, so make sure you know what to do with it.

Failures and alerts

• Device offline or Bridge not responding: the alert "Device not responding". Jobs wait and print by themselves once connectivity returns. Check the computer running Bridge, the power supply and the cable.
• Out of paper: status "Problem" and the "Device reports a problem" alert with a description. Refill the paper.
• Late "printed" result: always accepted, because the document physically exists. If it came from a device from which the job had earlier been redirected, the log will show "Alarm: possible duplicate printout": check whether two documents came out.
• Amount mismatch between the document and the device: the critical alarm "Alarm: document and device amount mismatch". Do not retry; compare the receipt with the source document and consult your accountants.

The "Audit log" in the job window is an immutable record of the run (creation, device selection, fetching, result, retries, manual decisions) showing who acted: the system, a user or the device. The same document requested again with the same key does not create a second job.

Where to find it in the app

• "Sales" menu, "Cash registers and printers", "Queue" tab ("Status" and "Device" filters, "Clear filters" button); shortcut in "Overview".
• Jobs can be handled by fiscal:write, a cashier with pos:write and a warehouse worker with shipping:write; viewing requires fiscal:read. The module requires the `fiscal` business profile feature.