Commands / printing

Before you start

Keep the task and command/job references. Viewing and changing require the appropriate permissions.

Steps

  1. Filter posting by open, conflict, failed or all and read reasons and attempt counts.
  2. For UNKNOWN inspect task details first. For RETRY_WAIT check source connection and permissions before Check now.
  3. Inspect remote print results. For partial or unknown SortingGo results, review physical output before deciding in manual review.

Verify the result

Confirm posting and printing independently. Reprints have a new record and reason and do not change shipment results.

Notes and examples

Timeout can mean a lost response rather than no action. Reprints are distinct from retrying an original request.

Limitations

Never blindly resend unknown results. A completed service response does not prove physical paper output.

Troubleshooting

Check service, printer, remote job and per-record results; prevent duplicate labels and share only non-secret diagnostics with administrators.

Frequently asked questions

What is Commands / printing for?

Track posting commands, print jobs and Odoo reservation reconciliation separately.

What do I need before using Commands / printing?

Keep the task and command/job references. Viewing and changing require the appropriate permissions.

How do I use Commands / printing?

Filter posting by open, conflict, failed or all and read reasons and attempt counts. For UNKNOWN inspect task details first. For RETRY_WAIT check source connection and permissions before Check now. Inspect remote print results. For partial or unknown SortingGo results, review physical output before deciding in manual review.

How do I verify the result in Commands / printing?

Confirm posting and printing independently. Reprints have a new record and reason and do not change shipment results.

What should I keep in mind in Commands / printing?

Timeout can mean a lost response rather than no action. Reprints are distinct from retrying an original request.

What are the limitations of Commands / printing?

Never blindly resend unknown results. A completed service response does not prove physical paper output.

How do I troubleshoot Commands / printing?

Check service, printer, remote job and per-record results; prevent duplicate labels and share only non-secret diagnostics with administrators.

This page matches the help inside DistributionGo (content version 2026.10.21.2).

← Back to the Help Center