Skip to main content

dgii-unavailable

HTTP 504 · Retryable. ERPly Pro retries automatically via the submission queue.

DGII did not respond within the configured SLA (15 s for RecepcionECF, 10 s for TrackStatus).

Typical causes​

  • Scheduled DGII maintenance (usually announced via Twitter/email by DGII).
  • Load spikes around month-end.
  • Network issues between AWS and the DGII servers.

How to proceed​

  • ERPly Pro already retries the submission automatically with exponential back-off (US-EP-07). You do not need to retry manually.
  • The document remains in pending state until DGII responds.
  • For live availability, query GET /v1/check-dgii-status/idCompany/{id} or the service status.