EVENT_MAX_RETRIES

Example response

When this error occurs, the API returns a JSON response with the following shape:

{
  "type": "https://docs.beel.es/errors/EVENT_MAX_RETRIES_EXCEEDED",
  "title": "EVENT_MAX_RETRIES_EXCEEDED",
  "detail": "Maximum retry limit of {0} reached for this event",
  "instance": "/v1/<resource>",
  "errors": [],
  "success": false,
  "error": {
    "code": "EVENT_MAX_RETRIES_EXCEEDED",
    "message": "Maximum retry limit of {0} reached for this event",
    "details": {}
  },
  "meta": {
    "timestamp": "2026-05-21T10:00:00Z",
    "request_id": "4bf92f3577b34da6a3ce929d0e0e4736"
  }
}

The type URI is stable and always resolves to this page.

Message

Maximum retry limit of {0} reached for this event

Se ha alcanzado el límite máximo de {0} reintentos para este evento

S''ha assolit el límit màxim de {0} reintents per a aquest esdeveniment

Send the request with Accept-Language: <es|en|ca> to receive the message in your preferred language.

Tokens like {0} are runtime arguments — the backend fills them with actual values before responding.

Other errors in this category

COMPANY_NOT_ACTIVATED_IN_ENVIRONMENT

This company is not activated in {0} mode. Activate it in that mode before connecting the payment provider: activation is what creates the invoice series and tax configuration that charges need