Errors
internal_ error
500. Something failed on Filmo's side, or the store that counts the rate limit was unavailable (the API does not let the request through unmetered). With an Idempotency-Key, a 500 can happen after the write was committed (the response could not be built); that error is then stored and replayed with Idempotent-Replay: true for 24 hours, so resending does not write twice and does not recover either. HTTP 500.
- HTTP status
- 500
- Problem type
- https://docs.filmo.io/errors/internal_error
Example
When it happens
500. Something failed on Filmo's side, or the store that counts the rate limit was unavailable (the API does not let the request through unmetered). With an Idempotency-Key, a 500 can happen after the write was committed (the response could not be built); that error is then stored and replayed with Idempotent-Replay: true for 24 hours, so resending does not write twice and does not recover either.
What to do
Note the requestId (it is also the X-Request-Id header). If the request was a write, read the resource to see where it stands before doing anything else. If the same request keeps failing, contact support with the requestId.
Retry
Stop500 internal_error · Idempotency-Key: Yes · Idempotent-Replay: true
Stop. The failure happened after the commit and is stored and repeated for 24 h with that key: read the resource to see where it ended up.
Retry with backoff500 internal_error · Idempotency-Key: Yes
Retry with exponential backoff and the same key.
Read the resource first500 internal_error · Idempotency-Key: No
Read before retrying a write: without a key nothing protects you from a duplicate.
Returned by
internal_error can be returned by any operation.
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?