report-expired
| Type URI | https://docs.vertama.com/Products/DIGT/problems/report-expired |
| HTTP status | 410 Gone |
| Endpoint | GET /api/digt/v1/reports/{id} |
Availability
Ships with the RFC 9457 error contract for the DIGT API. Until your instance runs that release, the endpoint returns a body-less 410.
The report existed, but its payload (including the receipt PDF) was removed by the retention cleanup before it was retrieved. The result is no longer available. Distinct from report-already-retrieved: nothing consumed this report — it aged out.
{
"type": "https://docs.vertama.com/Products/DIGT/problems/report-expired",
"title": "Gone",
"status": 410,
"detail": "Report 'DIGT-2024-00123' fell out of the retention window; its payload is no longer available",
"instance": "/api/digt/v1/reports/DIGT-2024-00123"
}
What to do
Retrieve results within the retention window — ideally promptly after
dispatch, cyclically while PENDING. If you see this regularly, your
polling cadence is slower than the retention window.