Connector error

Connector error

A failing connector often stops the entire run. This page helps you read the error, fix configuration, and avoid duplicate side effects.

1. Read the run and failing node

1. Open Runs for the workflow.
2. Select the Failed run.
3. Find the red node: error message and masked output (secrets are never shown).

Technical details are filtered; you still see the error class (HTTP 401, Dolibarr permission, timeout, etc.).

2. Common causes by family

Dolibarr

• Missing permission on the object (read, create, delete).
• Invalid fk_soc or id for the current entity.
• Locked or draft object not validated.

HTTP / Webhook

• Wrong URL, TLS certificate, or outbound firewall.
• Malformed headers or body (invalid JSON).
• 4xx / 5xx responses: use status and body in the run output.

Email

• SMTP not configured (often disabled on the shared demo).
• Expired SMTP credentials or blocked port.

AI

• Missing, expired, or revoked credential / API key.
• Provider quota exceeded or model unavailable.

Logic

• If branch without a default path.
• Misconfigured loop or delay.

3. Retry and idempotency

• Knot may retry transient errors (network, 503).
• For create actions (invoice, third party), enable idempotency when supported so retries do not duplicate data.

4. Escalation

Situation	Action
Reproducible in Simulate	Fix node config before enabling in production.
Intermittent error	Check timeout, server load, third-party API limits.
Error after Knot upgrade	Read the CHANGELOG and retest a minimal workflow.

Cuidado

Never paste API keys, passwords, or tokens into support tickets. Store secrets only in Knot credentials.

See also

• Performance and limits — when errors look like timeouts or saturation.
• Workflow does not run — when no run appears at all.