DataShift Logo

Public Error Catalogue

EDI Errors

DataShift publishes canonical public error codes for integration handling and support. Raw ingestion and validation failures are mapped to stable codes, with aliases shown when an older or lower-level code may appear in logs.

What to store

Store the canonical code, document type, business reference, and correlation id for support-safe troubleshooting.

What to retry

Retry only when the code is marked retryable. Validation and authentication failures usually need corrected input.

What aliases mean

Aliases are raw or legacy codes that resolve to the documented public code for customer-facing handling.

Showing 17 of 17 public codes.

Ingestion

Request authentication, duplicate detection, and payload acceptance.

5 codes

Authentication Required

AUTHENTICATION_REQUIRED

AUTHENTICATIONhighnot retryable

Aliases: MISSING_AUTH

Authentication credentials were not supplied with the request.

The request reached DataShift without credentials that can identify the integration token or submitting system.

Common causes

  • Authorization header was omitted
  • The HTTP basic authentication username or password was not sent
  • The submitting system stripped credentials while forwarding the request

Resolution

  • Send the request again with the configured authentication method
  • Verify the integration token and credential placement in the sending system
  • Confirm that any proxy or middleware preserves authentication headers

Send support

  • correlationId
  • request timestamp
  • sender system
  • authentication method

Access Denied

ACCESS_DENIED

AUTHENTICATIONhighnot retryable

Aliases: INVALID_CREDENTIALS, TOKEN_INACTIVE

The supplied credentials are not authorized to submit this document.

The submitting system was identified, but the token or credentials are inactive, invalid, or not permitted for the requested document flow.

Common causes

  • The token has been disabled or rotated
  • The request used credentials from another environment
  • The submitting account is not enabled for this document type

Resolution

  • Verify that the active token is being used
  • Check whether credentials were recently rotated
  • Confirm the document type is enabled for the integration

Send support

  • correlationId
  • token reference
  • document type
  • environment

Payload Missing

PAYLOAD_MISSING

VALIDATIONmediumnot retryable

Aliases: EMPTY_DOCUMENT, RAW_CONTENT_MISSING

The submitted document payload was empty or missing.

DataShift could not process the document because no usable document body was supplied.

Common causes

  • The request body was empty
  • The document upload completed without content
  • The sending system sent metadata without the document payload

Resolution

  • Resend the document with a non-empty payload
  • Check the sending system's request body configuration
  • Confirm the content type and body encoding match the integration setup

Send support

  • correlationId
  • content type
  • payload size
  • request timestamp

Duplicate Document

DOCUMENT_DUPLICATE

VALIDATIONlownot retryable

This document appears to have already been submitted.

DataShift detected that the same document content or business reference has already been processed or accepted.

Common causes

  • The sender retried after a timeout even though the first submission succeeded
  • The same business document was exported more than once
  • A resubmission was attempted without using the correction workflow

Resolution

  • Check the existing document using the correlation or business document number
  • Use the resubmission workflow when correcting an already-submitted document
  • Ensure the sending system treats successful acknowledgements as final

Send support

  • correlationId
  • business document number
  • document type
  • submission timestamp

Resubmission Conflict

RESUBMISSION_CONFLICT

VALIDATIONmediumnot retryable

Aliases: RESUBMISSION_INELIGIBLE

The document cannot be resubmitted in its current state.

The correction or resubmission request does not match the current lifecycle state of the original document.

Common causes

  • The original document has already advanced beyond the correction window
  • The resubmission does not reference an eligible original document
  • A correction was sent for a document that was not denied or awaiting correction

Resolution

  • Check the current document status before resubmitting
  • Use the original correlation or business document reference
  • Contact support if the document state looks incorrect

Send support

  • correlationId
  • original document id
  • business document number
  • current status

Received

Syntax, structure, schema, and business validation on the submitted document.

5 codes

XML Syntax Error

VAL_XML_SYNTAX_ERROR

PARSINGmediumnot retryable

Aliases: XML_SYNTAX_ERROR, PARSE_FAILED

The XML document could not be parsed.

The document is not well-formed XML, so validation and transformation could not continue.

Common causes

  • Missing or mismatched XML tags
  • Invalid character escaping
  • Truncated document content

Resolution

  • Validate the XML with a parser before sending
  • Check for truncation during file transfer
  • Escape reserved XML characters in text values

Send support

  • correlationId
  • document type
  • line or parser message
  • sender system

DTD Validation Failed

VAL_DTD_VALIDATION_FAILED

VALIDATIONmediumnot retryable

Aliases: DTD_VALIDATION_FAILED

The XML document does not match the required DTD structure.

The XML is well formed, but its elements or order do not match the expected document type definition.

Common causes

  • Required elements are missing
  • Elements appear in the wrong order
  • The sender used a different document profile than the configured integration

Resolution

  • Compare the XML against the published document structure
  • Confirm the sender is using the expected document profile
  • Correct the source export template and resend

Send support

  • correlationId
  • document type
  • validation message
  • sender profile

Schema Validation Failed

VAL_XSD_VALIDATION_FAILED

VALIDATIONmediumnot retryable

Aliases: XSD_VALIDATION_FAILED

The document does not match the required schema.

The document structure or field values failed schema validation for the configured document type.

Common causes

  • A required field is missing
  • A value has the wrong type or format
  • An enum or code value is outside the allowed set

Resolution

  • Validate the payload against the published schema
  • Correct required fields, date formats, and enum values
  • Refresh the sender export configuration if the schema version changed

Send support

  • correlationId
  • document type
  • schema version
  • validation path

Business Rule Violation

VAL_BUSINESS_RULE_VIOLATION

VALIDATIONmediumnot retryable

Aliases: BUSINESS_RULE_VIOLATION

The document failed business validation.

The payload shape is valid, but one or more business rules required by the document flow were not satisfied.

Common causes

  • Totals do not match the line values
  • Required party or location references are missing
  • A lifecycle reference does not match the related document

Resolution

  • Check totals, quantities, currency, and tax values
  • Verify related purchase order, acknowledgement, shipment, or invoice references
  • Correct the source data and resend the document

Send support

  • correlationId
  • business document number
  • document type
  • failed rule

Field Extraction Failed

VAL_FIELD_EXTRACTION_FAILED

VALIDATIONmediumnot retryable

Aliases: FIELD_EXTRACTION_FAILED

DataShift could not extract required fields from the document.

The document was readable, but required values could not be located or interpreted for canonical processing.

Common causes

  • The sender changed element names or nesting
  • A required value is present in free text instead of the expected field
  • The integration configuration expects a field that is absent for this partner

Resolution

  • Compare the submitted document with the configured field paths
  • Restore the expected sender format or update the integration configuration
  • Resend after required values are available in structured fields

Send support

  • correlationId
  • document type
  • field name
  • sender profile

Validated

Transformation into the canonical public EDI contract.

4 codes

Date Could Not Be Parsed

VAL_DATE_001

VALIDATIONlownot retryable

A date or date-time value could not be parsed.

A document date is missing required formatting information or contains an invalid date value.

Common causes

  • The date is not ISO 8601 formatted
  • A date-time value is missing timezone information
  • The source value contains an impossible calendar date

Resolution

  • Use ISO 8601 dates such as YYYY-MM-DD or full date-time values with timezone
  • Confirm the sender exports dates consistently
  • Correct invalid date values before resending

Send support

  • correlationId
  • document type
  • field path
  • submitted value

Canonical Schema Validation Failed

VAL_CANONICAL_SCHEMA_VALIDATION_FAILED

VALIDATIONmediumnot retryable

Document does not conform to the canonical schema for its document type

The transformed canonical payload did not satisfy the public JSON Schema contract for its document type.

The integration output is missing required fields or contains fields the canonical schema does not allow. Check the integration configuration for missing required targets and re-activate.

Common causes

  • Integration configuration is missing rules for required canonical fields
  • Integration configuration output uses field names that are not in the canonical schema
  • Snapshot the integration configuration was authored against has drifted from the runtime canonical schema

Resolution

  • Open the integration configuration in the editor, click Validate, and add rules for missing required fields
  • If the runtime canonical has bumped major version, refresh the snapshot and re-author

Send support

  • correlationId
  • document type
  • schema version
  • validation path

Integration Configuration Not Found

SVC_MAPPING_NOT_FOUND

SERVICEShighnot retryable

Aliases: MAPPING_NOT_FOUND, SENDER_MAPPING_MISSING, SCHEMA_NOT_FOUND

No active integration configuration was found for this document.

DataShift could not find the configuration needed to transform the submitted document into the canonical EDI contract.

Common causes

  • The document type has not been configured
  • The partner profile does not have an active mapping
  • The request used a token for the wrong trading relationship

Resolution

  • Activate the correct integration configuration for the partner and document type
  • Confirm the token belongs to the expected trading relationship
  • Retry after the configuration is published

Send support

  • correlationId
  • document type
  • partner reference
  • token reference

Transformation Failed

TRANS_MAPPING_PROCESS_FAILED

TRANSFORMATIONmediumnot retryable

Aliases: MAPPING_ERROR, MAPPING_PROCESS_FAILED, MAPPING_LOAD_FAILED

The document could not be transformed into the canonical format.

The integration configuration ran but could not produce a valid canonical document.

Common causes

  • A required source value is missing
  • A transformation rule produced an invalid value
  • The source document shape changed after the configuration was authored

Resolution

  • Validate the integration configuration against the latest sample payload
  • Check required field rules and default values
  • Correct the source data or update the transformation rules

Send support

  • correlationId
  • document type
  • configuration version
  • failed field

Services

Document-level processing, persistence, retry, and resolution workflows.

2 codes

Document Validation Failed

SVC_DOCUMENT_VALIDATION_FAILED

SERVICEShighnot retryable

The document type could not be determined.

The document reached services processing but failed document-level validation before it could advance.

The canonical JSON is missing the docType field.

Common causes

  • Canonical JSON missing docType field
  • Integration configuration produced invalid canonical structure

Resolution

  • Re-ingest the original document
  • Check the source integration configuration

Send support

  • correlationId
  • document id
  • document type
  • business document number

Line Number Resolution Failed

VAL_LINE_NUMBER_RESOLUTION_FAILED

VALIDATIONmediumnot retryable

Aliases: LINE_NUMBER_RESOLUTION_FAILED

One or more line numbers could not be mapped back to the original purchase order. Manual matching or confirmation is required.

A child document line could not be matched back to the original purchase order line automatically.

This occurs when the accounting system's line numbers differ from the receiver's PO line numbers and cannot be automatically resolved via the unique line key. This typically happens when a line was added or modified directly in the accounting system.

Common causes

  • A line was added or changed after the original purchase order was accepted
  • The child document omitted the original unique line key
  • The sender used accounting-system line numbers instead of the receiver's original line references

Resolution

  • Provide the original purchase order unique line key where available
  • Review and manually match the unresolved line
  • Correct the source line reference and resend if manual resolution is not appropriate

Send support

  • correlationId
  • purchase order number
  • line number
  • unique line key

Delivery

Transient dependencies and downstream delivery operations.

1 codes

Service Temporarily Unavailable

SERVICE_TEMPORARILY_UNAVAILABLE

EXTERNALhighretryable

Aliases: SERVICE_UNAVAILABLE, SERVICES_CLIENT_UNAVAILABLE, PUBLISH_FAILED, TOPIC_NOT_CONFIGURED

A temporary service dependency prevented the document from advancing.

The document could not be advanced because a required platform dependency was unavailable at the time of processing.

Common causes

  • A downstream service was temporarily unavailable
  • Event delivery was delayed
  • The receiving system or platform dependency returned a transient error

Resolution

  • Retry the document after the dependency recovers
  • Check whether DataShift has already scheduled an automatic retry
  • Contact support if the document remains blocked

Send support

  • correlationId
  • document id
  • document status
  • last retry time