Errors

`service_unavailable`

503. The feature the operation writes to is switched off for the account, and Filmo controls that switch. The request is correct. The spec documents it for the operations that create, update or delete an unavailability on a space, while space unavailabilities are switched off. HTTP 503.

HTTP status: 503
Problem type: https://docs.filmo.io/errors/service_unavailable

{
  "type": "https://docs.filmo.io/errors/service_unavailable",
  "title": "Service unavailable",
  "status": 503,
  "code": "service_unavailable",
  "detail": "This feature is not available for the account right now",
  "requestId": "req_0b9f6c1d2e3a4f5a8b7c6d5e4f3a2b1c"
}

When it happens

503. The feature the operation writes to is switched off for the account, and Filmo controls that switch. The request is correct. The spec documents it for the operations that create, update or delete an unavailability on a space, while space unavailabilities are switched off.

What to do

Do not retry: the answer does not change until Filmo switches the feature on, and an administrator of the account cannot do it. Stop sending these requests, and ask Filmo support if you need the feature.

Retry

Stop503 service_unavailable
Do not retry: the feature is switched off for the account.

Returned by

3 operations

POST /api/v1/availability/unavailabilities — Declare an unavailability
PATCH /api/v1/availability/unavailabilities/{unavailabilityId} — Correct or close an unavailability
DELETE /api/v1/availability/unavailabilities/{unavailabilityId} — Delete an unavailability

Through MCP

A tool call that fails comes back with `isError` set and the problem as structured content, with the same `code`.

Was this page helpful?

Example

When it happens

What to do

Retry

Returned by

Through MCP