Troubleshoot Integrations
Fix failed OAuth, manual credential, import, sync, mailbox, calendar, and payment connections.
Use this page when an integration will not connect, sync, import, or stay connected.
OAuth Connection Failed
Check that:
- You started the connection from the correct Agiled workspace.
- You approved the requested provider permissions.
- You returned to Agiled after the provider authorization page.
- Your provider account can access the selected company, workspace, calendar, project, list, or tenant.
Then try connecting again from Settings > Apps or the feature-specific settings page.
If the provider shows more than one account, tenant, calendar, mailbox, or workspace, pause and choose the one that owns the data Agiled should use. Connecting the wrong provider account can succeed technically while syncing the wrong records.
When reconnecting, use the same Agiled workspace where the integration will be used. OAuth grants are workspace-specific, so connecting from the wrong workspace can make the expected module look broken later.
Manual Credential Failed
Check that:
- The API key, token, secret, webhook URL, host, port, username, and password are copied exactly.
- The provider credential is active.
- The credential belongs to the correct provider environment.
- The provider account still allows API access.
For manual credentials, copy values from the provider dashboard directly and avoid extra spaces. If the provider supports separate live and test credentials, label the Agiled connection clearly so users know which environment they are testing.
Import or Sync Failed
Open the app detail panel and read last error or the most recent run. Fix the provider issue, then run Import or Sync again.
Common causes include expired OAuth access, missing permissions, provider rate limits, deleted provider records, invalid manual credentials, or selecting the wrong provider account.
Before rerunning a large sync, try the smallest safe scope the integration allows. Confirm one expected record appears or updates correctly in Agiled, then run the broader import. This avoids creating many duplicates from a bad mapping or wrong source account.
Mailbox Sync Failed
Open Settings > Mailboxes and check the connected mailbox row. Use Sync now after correcting the provider account. Use Backfill if recent sync works but older messages are missing.
If sending works but incoming sync does not, troubleshoot mailbox sync and provider permissions. If incoming sync works but sending fails, check SMTP or provider send permissions, sender identity, and rate limits.
Calendar Availability Looks Wrong
Confirm the correct calendar account is connected, the calendar still exists in the provider account, and the scheduling availability rules in Agiled are still correct.
Payments Do Not Work
Confirm the payment gateway is connected in Settings > Finance, the provider account is approved for live payments, and the public payment link belongs to the correct workspace.
Compare Agiled with the provider dashboard before retrying a customer payment or adding a manual payment. The provider may have captured, rejected, or held the payment even when the Agiled page has not updated yet.
Evidence to Collect
For support, collect the integration name, connected account, workspace, failed action, exact record or public link, timestamp, last error, and provider dashboard status. Do not include secrets, app passwords, API keys, or OAuth tokens in support notes.