Integration Errors

Integration Errors

Connection and authentication failures have a small number of causes. This page maps the error you see to the fix.

Where to Read the Error

Open Action Logs and select the task. Each tool call records the error the external service returned, verbatim. That text is more useful than the summary in chat, because it names the field, the permission, or the transition that was actually refused.

"Token expired" or "Connection expired"

Cause. OAuth tokens expire on a schedule set by the provider. This is routine, not a fault.

Fix. The owner of the connection opens Settings > Integrations > Connectors and clicks Reconnect. Connections belong to individuals, so an Admin cannot reconnect on someone else's behalf.

"Insufficient permissions"

Cause. Your account in the external tool cannot reach the resource. Quickly acts with your access and never escalates beyond it.

Fix. Open the project, space, or record directly in the external tool. If you cannot reach it there, ask an administrator of that tool for access. Reconnecting will not help, because the token is already working correctly; it is the account behind it that lacks the permission.

"Rate limited"

Cause. Too many API calls to the external service in a short window, usually from a bulk request or several playbooks firing together.

Fix. Wait and retry. If it recurs, stagger scheduled playbooks so they do not all run on the hour, and narrow searches that pull large result sets.

"Site not accessible"

Cause. The external site is unreachable, or the account was moved to a different site or URL.

Fix. Confirm you can load the tool directly in a browser. If the site changed, disconnect the integration and connect again so Quickly picks up the new site.

Invalid Field Errors

Cause. The value does not exist in the target system: an issue type the project does not have, a status the workflow does not allow from the current state, a space key that does not exist, or a priority outside your scheme.

Fix. Ask Quickly what is available before retrying, for example @Quickly what issue types are available in MOBILE?. For status changes, Quickly reports the transitions the workflow actually permits.

The Tool Was Blocked

Not every stopped action is an error. If the log shows Blocked (Safety), Blocked (Member), or Blocked (Admin), a policy refused it rather than the external service. An Admin can adjust that in Settings > General or per integration. See Autonomy Controls and Safety.

The Integration Is Missing Entirely

An Admin can enable only a subset of an integration's tools for the workspace. If a capability you expect is absent rather than failing, check with an Admin before assuming a fault. See Managing Integrations.

Escalating

If the error is none of the above, email support@askquickly.ai with the task from Action Logs and the verbatim error text.