A ticket did not print — what to check

Work through these in order. The first three cover the large majority of cases.

1. Is the bridge running?

Check the machine the printer is attached to. Is it switched on, logged in, and is the Penahak desktop application running? The bridge cannot poll if the machine is logged off. Tickets are not lost — they are queued — but nothing prints until it comes back.

2. Is the job in the queue?

Look at the print job for that order. Its state tells you where the problem is:

• No job was created — this is a routing problem, not a printing problem. Go to step 3.
• Job pending — the bridge is not picking it up. Back to step 1, or check network access.
• Job failed — the bridge tried and the printer rejected it. Go to step 4.

3. Is the item routed?

If no job was created, one of the three mappings is missing:

• Does the item have a product group?
• Is that product group mapped to a station?
• Is that station mapped to a printer?

A dish added to the menu recently and never assigned a product group is the classic cause.

4. Is the printer healthy?

• Paper, and paper the right way round.
• Cover fully closed.
• Cable connected, or network printer reachable.
• Can Windows print a test page to it right now?

If Windows cannot print to it, fix that first — the bridge can only do what the operating system allows.

5. Reprint

Once the cause is fixed, reprint the ticket from the order. You do not need to re-enter the order.