reservation_update_failed
Changing the reservation failed for a reason that is not about the request. Re-read the reservation, then retry.
HTTP 502An upstream channel failed to complete the request. Safe to retry with backoff.
When it fires
Changing the reservation failed for a reason that is not about your request and is not covered by a more specific code. The status mirrors the failure — 502 when it is unknown.
Response shape
Every Repull error follows the same envelope. The code is stable and safe to switch on.
{
"error": {
"code": "reservation_update_failed",
"message": "Reservation update failed",
"fix": "See https://repull.dev/docs/errors for recovery steps.",
"docs_url": "https://repull.dev/docs/errors/reservation_update_failed",
"request_id": "req_01J5X7Y8Z9ABCDEF12345678"
}
}How to fix
- Re-read the reservation with `GET /v1/reservations/{id}` — the change may have applied.
- If it did not, retry with backoff.
- If it keeps failing, email hello@repull.dev with the `request_id`.
Examples
curl
curl https://api.repull.dev/v1/reservations/215708 \ -H "Authorization: Bearer sk_live_YOUR_KEY"
TypeScript
const { error } = await res.json()
if (error?.code === 'reservation_update_failed') {
const current = await fetch('https://api.repull.dev/v1/reservations/215708', {
headers: { Authorization: `Bearer ${process.env.REPULL_API_KEY}` },
}).then(r => r.json())
// compare current.checkIn / checkOut with what you asked for before retrying
}If you're an AI agent
The change failed for an unknown reason. Re-read the reservation to see whether it applied, then retry with backoff. Report the request_id if it persists.
Related
- Error reference — the full table of error codes
- Using Repull from AI agents — patterns for handling errors in agent loops
- Update a reservation
Hit an error that isn't covered? Email hello@repull.dev with the request id from the response headers.
AI