reservation_window_not_covered (409)
reservation_window_not_covered
HTTP status: 409
Retryable: No. Retrying without changes will fail the same way.
A reservation session cannot stay open until the reservation due time, so it was not created.
When it fires
Only the connected-system integration that starts sessions for reservations receives this code. A request made with an API key never receives it. The integration asked for a session that must stay open until the reservation due time, and the session lifetime ends before that time. The integration also receives it when the due time is already past. No session, applicant, or event is created.
How to handle it
No action is necessary. If the session lifetime ends before the due time, the integration does not start the session now. It starts one later, inside the verification window of the reservation. If the due time is already past, no session is started for that reservation.
Example response
{
"error": {
"type": "https://docs-dev.autohost-dev.uk/api/errors/reservation_window_not_covered",
"code": "reservation_window_not_covered",
"message": "The session cannot stay open until the reservation due time. The due time is too far in the future, or it is already past.",
"request_id": "req_01HEXAMPLE0000000000000000",
"doc_url": "https://docs-dev.autohost-dev.uk/api/errors/reservation_window_not_covered",
"details": {
"reason": "session_ends_before_due"
}
}
}