A connector test failed — one-click fixes
1 min · 4 steps
When 'Test' fails, Avery classifies the failure and offers the exact one-click fix — re-link, re-enter the key, or correct host & port.
When a connector's 'Test' fails, Avery doesn't just show a red error — it works out WHY it failed (a bad credential, an unreachable host, a misconfigured field, or a capability that isn't wired yet) and offers the precise next step as a one-click button right on the card. The raw error is still shown underneath as the detail. Every fix you apply is recorded in the Activity stream.
Steps
- Auth failed — re-link or re-enter your key.
A wrong / expired credential (a 401/403, or a revoked OAuth token) offers 'Re-link' on OAuth connectors (rotates the token in place — your agents keep working) or 'Re-enter API key' on key-based ones (opens the connector form focused on the secret field). A stronger AI model can't fix a bad key, so this is always a human one-click.
- Couldn't reach the host — check host & port.
A network/timeout failure offers 'Check host & port' — it opens the form focused on the host field so you can correct an address or VPN setting, then re-test. Useful for self-hosted bridges (e.g. a Sage 100 bridge reached over WireGuard).
- Missing config — fix the flagged field.
A configuration failure (a required field empty or wrong) opens the form focused on exactly the field to correct, with a hint banner, so you don't hunt for it.
- Not wired yet.
If the failure is 'this capability isn't implemented for this provider', there's nothing to one-click — the card just explains it so you know it's not your setup.
Live recipes need the desktop
This article is a static preview. The in-app Help sidecar inside Avery NXR can fire each step against your live project — install the desktop to use it interactively.