You may notice recurring authentication failures between Aircall and Salesforce, visible as repeated prompts in the Aircall Dashboard to re-authenticate your Salesforce integration. This article explains why it happens and how to fix it.
Why this happens
Salesforce allows up to five active OAuth authorizations per Connected App per user. When a sixth is requested, the oldest token is automatically invalidated. If that token belongs to Aircall, the integration fails.
NOTE: This limit is enforced by Salesforce, not Aircall. It applies per user, per Connected App, across all integrations sharing the same Salesforce instance.
This issue commonly occurs when multiple integrations access the same Salesforce instance concurrently.
How to solve it
Limit simultaneous integrations
Keep no more than 4 to 5 concurrent integrations per Salesforce account to stay within Salesforce's OAuth authorization limit.
Audit connected app authorizations
Review your active tokens and remove any that are old or unused to free up authorization slots.
Steps:
- In Salesforce, go to Setup > Connected Apps > OAuth Usage.
- Identify old or unused tokens.
- Remove any tokens that are no longer needed.
For more details, please see Salesforce's documentation on managing OAuth-enabled Connected Apps access to your data.