message-unavailable
| Type URI | /api/docs/problems/duba/message-unavailable |
| HTTP status | 503 Service Unavailable |
| Endpoints | GET /api/duba/v1/download/{id}; GET /api/egvp/v1/postboxes/{safeId}/messages/{messageId}/download |
The message could not be fetched because of a transient failure: the EGVP server was unreachable, or reading the message failed. Each such failure counts against the message. After a configured number of failures, the message is quarantined: it no longer appears in the message listing until an administrator intervenes.
{
"type": "/api/docs/problems/duba/message-unavailable",
"title": "Service Unavailable",
"status": 503,
"detail": "Message 1234 temporarily unavailable: connection refused",
"instance": "/api/duba/v1/download/1234"
}
What to do
Retry later, with growing pauses. When the message stays unavailable or leaves the listing, tell Vertama its id. Compare message-transfer-pending, the other 503 of this endpoint, which only asks for patience.