The document translation sometimes returns this error, and sometimes works normally, even for the same file

The error payload shows an intermittent service-side parsing failure:

• code: InternalServerError
• innerError.code: InternalServerErrorDocumentParsing
• target: Operation
• Message: "Document failed during parsing. If the error persists, report it with date/time of error, request identifier from response header X-RequestId, and client identifier from request header X-ClientTraceId."

This corresponds to the generic high-level error model used by Document Translation and related services, where:

• code is one of the standard high-level error codes such as InternalServerError, InvalidArgument, InvalidRequest, RequestRateTooHigh, ResourceNotFound, ServiceUnavailable, or Unauthorized.
• innerError provides a more specific error code and message for the failure.

Because the same file sometimes succeeds and sometimes fails, this aligns with a transient internal service issue rather than a permanent problem with the document or request parameters.

Recommended actions based on the error contract:

1. Implement retry logic
   • Treat InternalServerError and InternalServerErrorDocumentParsing as transient.
   • Retry the translation after a short delay when this error occurs.
2. Capture diagnostics for escalation
   • For each failed request, log:
     • Date/time of the error (UTC).
     • X-RequestId from the response headers.
     • X-ClientTraceId from the request headers (set and log this in the client).
   • These values are explicitly requested in the error message and are required for deeper investigation by Azure support.
3. Check status and error details via status APIs
   • When polling job or document status, inspect the status and error fields returned by:
     • Get status for a specific translation job or all jobs (status, summary, and error fields).
     • Get status for a specific document or all documents (status, characterCharged, and error fields).
   • Confirm that the failure is reported as Failed with InternalServerError in these status responses, which indicates a service-side issue rather than validation (ValidationFailed) or client errors (InvalidRequest, InvalidArgument, Unauthorized, etc.).
4. If the error persists for the same file
   • After adding retries, if the same document still fails repeatedly with InternalServerErrorDocumentParsing while others succeed, collect:
     • The failing document (or a redacted/repro version if needed).
     • The timestamps, X-RequestId, and X-ClientTraceId for several failed attempts.
   • Use these details when opening a support case so the service team can trace the internal failure.

The behavior described (intermittent InternalServerErrorDocumentParsing for the same file) is consistent with the documented error model for Document Translation and should be handled with retries and, if persistent, escalated using the identifiers specified in the error message.

References:

• Get status for a specific translation job
• Get status for a specific document
• Get status for all translation jobs
• Get status for all documents
• Get supported document formats
• DocumentTranslationError Class