Troubleshoot printing

Ask the AI assistant

Troubleshoot printing

Confirm posting first, then inspect the print job, remote result and physical paper. Printing is separate from shipment; reprinting must not repeat posting.

Identify the correct job

Record print ID, source task, template revision, remote job ID and error from the task or Operations and printing. Verify APPLIED first: field completion alone does not imply a shipment-label job exists.

Investigate its status

For FAILED, check Print Service reachability, revision, printer and paper. For UNKNOWN/partial completion, inspect remote results and count physical output. Fetch record results if the screen offers it. A timeout alone is not a reason to resend the whole batch.

Manual confirmation and selected reprint

When a SortingGo job offers manual review, check record states and original indexes. Select only eligible records genuinely missing, enter a reason and confirm paper inspection, then choose no reprint or selected reprint. If no records are selectable or evidence is insufficient, ask an administrator; do not falsely confirm. Other profiles request a reprint reason on screen.

Verify the outcome

A child reprint keeps its original-job link. Check its result and physical paper; original posting remains traceable. Reports should include sanitized version/job/error and missing range, never tokens, customer data or personal details on full labels.

May I reprint everything after a partial print?

First compare remote record results with paper. In manual review, select only eligible missing records and give a reason to avoid duplicates.

Why is there no print job after task completion?

COMPLETED is not shipment. Verify APPLIED and SHIPPED; shipment confirmation creates the print job.

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

← Back to the Help Center

AI Help Center

Ask the AI assistant Help Center