EDI Operations

Inspect order evidence, transport and acknowledgment outcomes, exceptions, explicit recovery, and current retention defaults.

Start an investigation with workspace, partner, document/reference, timestamp, and correlation ID. Preserve the original request and observations before making a recovery change. Orders and recovery covers uncertain generation.

Inspect the right outcome

Question	Surface
What is recorded against this partner/PO?	/v1/operations/orders/{partner_id}/{po_number}
What wire and findings were stored?	/v1/documents/{id} and /evidence
Did transport accept it?	/v1/deliveries/{id}/evidence, native upload jobs, Mail receipts
Did the partner acknowledge it?	/v1/reconciliation; outstanding=true or overdue=true
What business-chain evidence exists?	/v1/business-reconciliation, scoped lifecycle/evidence
Did Sync and the ERP accept it?	Sync delivery receipt and original-connection outcome

Order lists are bounded; the source returns at most 200 orders with a truncated flag. Do not treat loaded rows or a terminal filter as a complete history. Scope lifecycle and evidence by partner where references repeat.

curl --silent --show-error --fail-with-body \
  "${EDI_API_BASE:?Set your API base}/v1/reconciliation?overdue=true" \
  --header "Authorization: Bearer ${EDI_API_TOKEN:?Load your scoped key}"

A 997 means functional acknowledgment, not fulfillment or payment. Generated, queued, transport-accepted, functionally acknowledged, and business-complete are separate states. Missing receipt fields are unknown; historical receipts do not complete a current attempt.

Exceptions and deductions

/v1/operations/exceptions connects source failures to review cases, owners, deadlines, optimistic revisions, and immutable history. Read the latest case and source evidence before a PATCH. A review status cannot overwrite the source delivery outcome. Resolve revision conflicts by reading again and reviewing changed evidence.

Deductions support capture, categorization, dispute, evidence, and terminal outcomes through /v1/deductions. Partner-scoped evidence helps explain a dispute; an exported bundle does not establish the counterparty agreed or money was recovered.

Recover deliberately

Action	Effect and review scope
Reprocess stored inbound document	Revalidates/translates and may enqueue work; not a read
Redeliver	Requeues the identified transport attempt; inspect original destination and payload
Retry held automatic 855	Retains original order/date while explicitly reviewing current policy
Retry callback	Retains original event/payload/endpoint/key revision; receiver must deduplicate
Replay dead letters	Requeues dead-letter events in the credential’s scope; a local filter does not narrow it
Discard one dead letter	Permanent audited removal; can release an order lane
Flush outbox	Platform-admin action across the active outbox, not a customer-filtered send

Review downstream duplicate handling before any repeat. The CLI checks recovery receipt identity and counts; malformed HTTP 200 responses can remain outcome_unknown. Inspect state instead of automatically retrying. Requeue acknowledgment does not prove delivery.

Monitoring and audit

/v1/monitoring and /v1/status-board show current observations. Calling POST /v1/monitoring/evaluate can send configured alerts. Webhook and email alert channels are external effects; list/read operations are separate. The immutable audit log records actors and operations. Export evidence with its actual identifiers and timestamps.

Route	Authentication / purpose
/live	Public liveness; no database probe
/health	Public readiness; 503 when the database is unreachable
/metrics	Platform administrator; Prometheus

Retention defaults

Current source enables bounded retention. 0 disables a sweep; it is not the default. Sweeps run on the monitor leader and protect relevant pending work.

Setting	Default days	Scope
EDI_DOCUMENT_RETENTION_DAYS	400	Documents/raw detail, subject to pending-work and receipt references
EDI_USAGE_RETENTION_DAYS	400	Usage ledger
EDI_SEEN_RETENTION_DAYS	400	Interchange deduplication entries
EDI_ACK_RETENTION_DAYS	400	Settled acknowledgment rows; pending rows protected
EDI_DELIVERY_RETENTION_DAYS	180	Terminal AS2/email deliveries; pending work protected
EDI_DEADLETTER_RETENTION_DAYS	90	Eligible dead letters; held order lanes protected

Pruning dedup entries reopens the replay window. Retention is not a complete tenant-erasure workflow; outbound receipts and frozen connection/key references need explicit handling. Review deployment and recovery evidence before depending on backups, rollback, or operating objectives.