connection_not_linked
A sync was requested on a connection that is not `active`.
A sync was requested on a connection that is not active.
| Code | connection_not_linked |
| Type | unprocessable_error — Well formed, but breaks a domain rule |
| HTTP | 422 |
| Retriable? | No |
What to do
A pending_link connection has never completed linking; a requires_relink one needs the user to go through link_url again. Either way there is nothing to sync yet.
Retrying the same request will fail the same way. Change the request, not the frequency.
The envelope
{
"error": {
"type": "unprocessable_error",
"code": "connection_not_linked",
"message": "…",
"hint": "A `pending_link` connection has never completed linking; a `requires_relink` one needs the user to go through `link_url` again. Either way there is nothing to sync yet.",
"retriable": false,
"doc_url": "https://docs.facturia.cl/errors/connection_not_linked",
"request_id": "req_01K2R7Q9M4T2VB"
}
}Program against code, never against message — the prose can be rewritten, the code cannot (§5.8).
hint and retriable arrive in the response with these exact values: they are a function of code and come from the same dictionary GET /v1/error_codes serves, so the envelope and the dictionary cannot disagree. Both are English on the wire by design — one registry, one language. More in The error envelope.
See also
Every code
The error envelope
The machine-readable copy of this page lives at GET /v1/error_codes, unauthenticated.