Start with the request and its reported state.

The Automation Service shows offline

Check that the service is running and its enrollment is approved. From its machine, check the configured Center address, certificate trust and Runner gateway. Enrollment uses the web/API connection; the ongoing service connection uses the separate gateway, whose default port is 9443.

The service initiates its Center connection. Configured local HTTP or TCP triggers have their own inbound access requirements. A connected service may also be waiting for documents or reporting an application error, so inspect its applied state before trying to print.

Review service setup → · Check addresses and HTTPS →

A print result stays at “sent”

Sent means the complete stream was transmitted or a local queue accepted the job, without confirmation from an acknowledgement-capable target. It can be the expected final result. Ordinary network zpl-raw, Windows RAW, Linux CUPS RAW and Windows GDI paths do not produce confirmed.

If the physical output is missing, inspect the selected destination, queue, media and printer messages. Keep the request identifier while investigating. Do not submit another request just to obtain a different status.

Held or unknown describes a different situation: the system cannot establish the print outcome. Investigate before deciding whether replacement labels are needed. A target acknowledgement also does not check physical alignment or barcode quality.

Understand connection outcomes → · Follow the recovery steps →

There is unexpected repeated output after reconnecting

Preserve the original and any repeated request records before submitting more work. Compare the idempotency keys, label versions, target, copy counts and timestamps. Also inspect pending jobs in the operating-system queue and at the printer.

Idempotency helps recognize the same request identity on its applicable path. A new key, an intentional repeat action or a new batch represents new work and can request output again. Reconnection alone does not prove the cause of repeated labels, and request deduplication cannot settle an unknown physical outcome.

If you cannot explain the extra output, report the product issue with the build version, request identifiers, connection type, messages and a synthetic reproduction where possible. Keep credentials and sensitive source data out of the report.

Keep the history that answers the question

Print Center and the archive show request and delivery information. Work dispatched through an Automation Service also has a service job and event history. Direct Center printing does not create a Runner job row. Follow the record for the actual execution path.

Investigate a print record → · Review the operating checklist →