100%
Hardware & Printing › Print Agent

Status screen, alerts and retries

The agent's Status screen, what each job state means, Retry and Reprint, and the alerts the agent raises when something fails.

The Status screen, opened from the Printers screen, is the agent’s record of what it has been asked to print. When something did not print, look here first.

Connection

The top of the screen shows the connection to the server:

  • Connected — receiving print jobs.
  • Reconnecting — the connection dropped and the agent is retrying. Jobs sent meanwhile wait on the server and print when it is back.
  • Disconnected — no jobs are received until it reconnects. Check the device’s network.

Recent jobs

Each job shows what it was — Receipt, Prep 1, Label 2, Drawer kick, Reprint, Test print, Gift card slip, Coupon, Trip ticket, Guest Wi-Fi slip — the printer, the time, and its state:

  • Pending — received, not printed yet.
  • Printing… — being sent to the printer.
  • Completed — printed. A note may say the printer did not confirm; that is normal for printers that cannot report status.
  • Failed — could not be printed after a retry; the reason is shown.

Retry and Reprint

  • Retry appears on failed jobs (and on waiting jobs that have already been tried). Fix the cause first — paper, power, cable, address — then press it to send the same job again.
  • Reprint appears on completed order jobs and prints another copy, marked as a reprint.

    pa-status-03
If a job you expected is not in the list at all, it never reached this agent. That points at Print Routing, or at an agent that belongs to a different store — not at the printer.

What happens when a job fails

  1. The agent opens a fresh connection to the printer and tries once more.
  2. If that fails too, the job is marked Failed with the reason.
  3. The agent raises an alert on the device naming the printer and the job.

A failed job is not retried again on its own; use Retry here, or reprint from the register.

Alerts

The agent also alerts when a printer it drives cannot be reached, and when it has been out of contact with the server for more than two minutes — by then tickets are waiting on the server and someone should check the network. The alert clears when the connection is back.

  • Android — heads-up notifications that stay in the notification shade; the permanent notification’s text changes with the state.

  • Windows — notifications in the corner and in the notification centre, even while the agent is minimised.
Alerts appear on the device the agent runs on. A box hidden in a cupboard alerts nobody — put it where someone will see its screen, or run the agent on a tablet at the pass.

A Windows printer that stops printing

A printer installed in Windows that is switched off, paused, offline or out of paper does not refuse tickets: Windows accepts each one and holds it in the printer’s queue, and the agent reports the job as completed. To catch that, the agent watches the Windows queue of every printer it prints to.

  • When tickets are still waiting after about a minute and a half, the computer shows Printer problem with the printer’s name, the number of tickets waiting, how long the oldest has waited and the reason Windows gives — for example Windows queue stalled: 7 tickets waiting, oldest 4 min (paused).
  • It repeats every two minutes while the tickets are stuck and stops by itself once they print.
  • Fix it in Windows: switch the printer on, add paper, or open the printer’s queue and resume it. The waiting tickets then print in order.
pa-queue-01
A receipt or kitchen printer on the network prints more reliably added to the agent as a Network printer than through a Windows driver: the agent then talks to it directly and knows at once when it does not answer (Adding printers to the agent).