A connection failed

• "Invalid grant" or "unauthorized" → the grant expired or was revoked. Reconnect.
• Permission or scope error → the authorisation completed without a required scope. Reconnect and approve all scopes.
• Rate limit or 429 → you are authorising too quickly. Wait before retrying.
• Works for a colleague, fails for you → you are not authorised for the underlying resource, or you are in a different workspace.
• Redirects back without connecting → the provider session was in a different account than expected. Sign out of the provider and retry.

1. 1Disconnect the existing connection if it is in a broken state.
2. 2Wait a few minutes if the failure was rate related.
3. 3Reconnect from the integrations area.
4. 4Approve every requested scope your policy allows.
5. 5Confirm the connected account label is correct.
6. 6Verify with a narrow read-only question.

Some providers require business verification, app review, or an administrator role before an authorisation succeeds. When that is the blocker, OpenbirdAI cannot help — the requirement must be satisfied on the provider side first.

• Re-check authorisation status if a connection suddenly stops working.
• Review unused connections quarterly and remove them.
• Document which account owns which connection.
• Keep workspace ownership of connections unambiguous.

Connection problems are often account-specific, which makes them confusing to diagnose alone. Two comparisons usually settle it.

• If a colleague can connect and you cannot, the blocker is your account or your role on the provider side.
• If you can connect and they cannot, check which workspace they are in and which account they authorised.
• If neither of you can connect, the provider requirement has probably changed.