Skip to content
SmartFACT HelpHandbooksWatch and practise
Handbooks: LabelRules

When the network drops

What the station pages show when the connection is lost while you prepare, accept or print a run, what is kept, what is sent again and what to check when it returns.

Review edition · 13 November 2026 · For Operator, Supervisor

On this page

This page is for a site that prints through PrintStation, when the device you work on loses its connection to LabelRules while you find a job, prepare or accept a label, or print a run. LabelRules has no offline mode: it records nothing while the device cannot reach it, and it keeps nothing on the device. For the computer and printer that PrintStation prints on, read A printer stopped printing.

What the pages show

LabelRules does not watch whether the device is online. When something you do gets no answer because the connection was lost, it says so under the field or button you used:

  • A job reference you scan moves to Last scan: ... in the field, no job opens, and under the field: "The connection was lost. No answer came back from LabelRules, and nothing was changed. Try again when the connection is back." A lookup changes nothing.
  • Prepare label and Accept ... labels change to Preparing… or Accepting… and then back, and under the button: "The connection was lost. No answer came back from LabelRules, so it is not known whether this was saved. Reload this page to check before you try again." LabelRules may have received the press before the connection went, or not: the message cannot tell which.
  • Reload this page, under that message, asks LabelRules for the page again and sends nothing you pressed. While the connection is still down the page stays as it is and the message says "The connection is still lost." Once LabelRules answers, it says "The connection is back. This page now shows what LabelRules has recorded: check whether what you sent is there before you try again." If LabelRules received your press and answered it with a message of its own, such as a refusal, that message now shows at the top of the page as well.
  • Print with PrintStation, or Send to the destination, shows "No answer came back. Check the job before trying again." The PrintStation panel does not open.
  • Send again to the destination, or a print that opened the PrintStation panel, may be recorded by LabelRules with only the run's page lost on the way back. Then, under the button: "The connection was lost. This was recorded, but no answer came back from LabelRules before this page could show it. Reload this page to see it before you go on." Press Reload this page, which only reads the page, rather than the button again. Once LabelRules answers, it says "The connection is back. This page now shows what LabelRules has recorded."

The message goes when you do the next thing, or open another page. The other buttons and links on LabelRules' pages say the same when the connection is lost. A page you open from the menu is loaded by the browser itself, which shows its own page when there is no connection.

What is kept, and for how long

Nothing is kept on the device, and the device sends nothing again by itself when the connection returns. What LabelRules has already received stays on LabelRules:

  • A preview can be accepted for five minutes, as the countdown on Review your label shows. After that, go back to the job and prepare the label again.
  • An accepted run keeps its labels waiting for 24 hours. A run with labels still waiting after that shows "Run held: execution deadline expired." Ask the Supervisor.
  • Copies already handed to PrintStation stay there. LabelRules keeps checking PrintStation for what happened to them, whether or not your device is connected.

When the connection returns

Press Reload this page under the message, or reload the page you were on, and check what it shows before pressing anything again.

  • Finding a job: scan the reference again.
  • Preparing: press Prepare label again. If the first press was received, LabelRules made a preview that nobody has accepted; it expires after five minutes and nothing prints from it.
  • Accepting: if the preview now offers Open accepted run, the first press was received: open the run. Pressing the accept button again on the same preview never makes a second run; it opens the run the first press made. Accepting another preview for a line whose run was already accepted is refused with "This fulfilment was already accepted. Use an explicit exact reprint with a reason."
  • Printing: open the run and read Copies and outcomes first. Pressing Print with PrintStation again is safe. It resends exactly the same request, which PrintStation recognises if it already arrived, or opens the panel again for copies PrintStation already has. It never sends a copy twice.

If LabelRules itself could not reach PrintStation, the run says "PrintStation did not answer. Nothing is resent automatically: try again to resend the same request." Press Print with PrintStation again once the connection is back.

At a site that prints unattended

Where the site's labels go to a PrintStation destination, accepting a run sends its labels there straight away, without anyone pressing Print. If LabelRules cannot reach PrintStation at that moment, it tries again by itself, about once a minute and always with the same request, so the labels go once PrintStation answers and are never sent twice.

PrintStation then keeps the labels for the destination's computer for the delivery window, which is eight hours unless your installation sets another. If that computer does not collect them in time, the run says "The delivery window ended before the printer took these labels. Nothing was printed." and offers Send again to the destination. Where a copy was already tried at the printer, only an exact reprint is offered: read Authorise an exact reprint.

If a label may already have printed

When a copy reached the printer and its outcome is not known, the run says "Output is uncertain. No uncertain copy will be resent automatically. Reconcile it in PrintStation; this run records PrintStation's result." Printing the run is not offered. Follow Handle uncertain PrintStation output. A network that has come back does not show whether an earlier copy printed.

While the connection is down

Do not print the labels another way while the connection is down, for example from the PDF proof: LabelRules would have no record of them. Keep the job reference, note which labels you already have and tell the Supervisor what happened when the connection returns.

LabelRules counts only the activity that reaches it. After 15 minutes with none, the next station page shows the lock, even if you were at the screen while the connection was down. Sign in again through SmartFACT Accounts. If Sign in again itself gets no answer because the connection was lost, the lock says so under the button: choose Sign in again once the connection is back. Whichever way the next sign-in starts on a device where someone has been running labels, by Sign in again, by reloading the page, or by Sign out and then Sign in with SmartFACT Accounts, locked or not, SmartFACT Accounts asks for that person's own email address and password, so the person signed in before cannot be signed back in by mistake. It keeps asking until someone has signed in. A print already sent still records its outcome while the station is locked.

What the Supervisor sees

LabelRules does not show anyone that a device has lost its connection. A run whose labels have not gone shows them waiting, and Print through PrintStation lists each block of up to 20 copies with what PrintStation last reported. Where the site prints unattended, Printer setup shows the printer's state and when PrintStation last heard from its app: read A printer stopped printing.