Recurring Invoices error codes
Every public API error code emitted by Recurring Invoices, with its HTTP status, its type and a page per code.
Error codes emitted by Recurring Invoices. Each code links to its own page with the cause and the action to take.
| Code | Type | HTTP | Description |
|---|---|---|---|
invalid_frequency_interval | invalid_request_error | 422 | The interval is lower than 1, so the recurrence would never advance to a next run. |
invalid_frequency_type | invalid_request_error | 422 | The frequency is outside the catalogue daily, weekly, biweekly, monthly, bimonthly, quarterly, semiannual, annual, custom. |
invalid_holiday_handling | invalid_request_error | 422 | The holiday policy is outside the catalogue skip, before, after, same. |
invalid_recurring_invoice_id | invalid_request_error | 400 | The recurrence reference received is not a valid identifier, usually because an internal value replaced the public id. |
invalid_recurring_invoice_uuid | invalid_request_error | 400 | The recurrence identifier in the path or in the payload is not a valid UUID. |
invalid_recurring_payment_terms_template | invalid_request_error | 422 | The payment schedule template of the recurrence, applied to every invoice it generates, is not valid. |
invalid_recurring_presentation_policy | invalid_request_error | 422 | The presentation policy of the recurrence, which sets how the invoices it generates are presented, has an invalid value. |
recurring_already_active | invalid_request_error | 422 | The recurrence is already running, so there is nothing to activate. Legacy code kept for compatibility: current endpoints report this as recurring_invoice_already_active. |
recurring_invoice_already_active | invalid_request_error | 422 | The recurrence is already running. |
recurring_invoice_already_cancelled | invalid_request_error | 422 | The recurrence was already cancelled, and cancellation is terminal. |
recurring_invoice_already_paused | invalid_request_error | 422 | The recurrence is already paused, so pausing it again changes nothing. |
recurring_invoice_cancelled_cannot_resume | invalid_request_error | 422 | A cancelled recurrence cannot be resumed: cancellation closes it for good, unlike a pause. |
recurring_invoice_cannot_run | invalid_request_error | 422 | The recurrence cannot generate an invoice right now: it is not running, its cycle is over, or it lacks the data an invoice needs. error.message states the specific reason. |
recurring_invoice_completed_cannot_resume | invalid_request_error | 422 | A completed recurrence cannot be resumed or activated: it has already used up its occurrences or passed its end date, so no generation is left pending. |
recurring_invoice_has_generated_invoices | invalid_request_error | 422 | The recurrence already produced invoices, and those invoices depend on it for their traceability. |
recurring_invoice_not_found | not_found_error | 404 | The identifier does not resolve to any recurrence of the authenticated company. |
recurring_invoice_requires_at_least_one_line | invalid_request_error | 422 | The recurrence has no lines, so every generated invoice would come out empty. |
recurring_not_active | invalid_request_error | 422 | The operation needs a running recurrence and this one is paused, completed or cancelled. Legacy code kept for compatibility with older integrations. |
recurring_presentation_activation_changed | conflict_error | 409 | The company switched its presentation system on or off twice in a row while the recurring invoice was being generated. The generation stopped without writing anything. |
recurring_presentation_policy_precondition_required | invalid_request_error | 428 | The change to the presentation policy did not state which version it is based on. |
recurring_presentation_policy_version_conflict | conflict_error | 409 | The presentation policy of the recurrence changed after you read it. |
recurring_presentation_unavailable | invalid_request_error | 422 | When a generation of the recurrence ran, the presentation it is configured to use was not available, so the invoice could not be generated. details.reason says what was missing. |
Related
Error codes by category
Find an error by the category that emits it.
Full reference table
All codes, HTTP statuses, types and descriptions in one reference.
Error model
Interpret the error envelope and handle errors by code.