Use distinct states
A confirmed invalid-input response is different from a timeout after transmission. Keep received, submitted, generated, reviewed and released separate. Record a non-secret request identifier where available. Do not call a report missing merely because your connection stopped waiting, and do not call it accepted because the provider returned a file location.
Preserve the facts before changing anything
Record when the attempt happened, which input and template versions were involved and the observed status. Keep sensitive content in its authorized storage, not a public issue or diagnostic log. Redact credentials and tokenized links. Compare the error with current official documentation before deciding whether the input, quota, route or service availability is responsible.
Reconcile an uncertain attempt
Use documented status or history facilities if available and within your access. If an output exists, compare its identity before using it. If its status cannot be established, hold the branch for its owner rather than repeatedly transmitting. Any retry should be deliberate and account for duplicate files, charges and downstream delivery effects.
Continue independent work safely
One unresolved report need not stop reviewing other clearly identified outputs. Keep blocked items visible with an owner and next action, while preventing them from entering the release queue. After resolving the cause, add a representative non-sensitive regression case. Preserve the earlier failure instead of rewriting the record as an uninterrupted success.
Worked queue entry
Record report R-004, template T-003, submitted at the observed time, result unknown after connection timeout, owner report editor, next action inspect documented generation history. Do not record a fabricated provider error or attempt count. Keep the original uncertainty after later reconciliation and append the actual finding. If a second output is discovered, identify which one is accepted and prevent accidental duplicate delivery through your authorized release process.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- CraftMyPDF: documented template workflow — Merchant documentation · craftmypdf.com · Merchant-controlled · checked 2026-09-30