Connected apps usually break after a Salesforce security update for one of four reasons: a deactivated user, missing permissions, tightened IP restrictions, or an incomplete app installation. Check the connected user's status first. Then review the OAuth and IP settings in Setup. Most disconnections resolve in under 15 minutes once you find the right setting.
Salesforce rolls out security updates on a regular schedule, and connected apps sometimes stop working right after. If you have noticed OAuth errors or a sudden integration failure, the cause is almost always one of a handful of known issues, not a mystery bug.
Here is how to find it and fix it.
Before you dig into settings, confirm two things:
A deactivated user or a missing permission breaks any app tied to that account. This takes two minutes to check and fix the problem more often than any other step on this list.
OAuth failures are the most common issue after a Salesforce security update. The connected app stops authenticating because Salesforce tightened its security posture, and IP restrictions are usually the reason.
To fix it:
Check with your IT team before you make this change. Relaxing IP restrictions restores connectivity, but it should still match your organization's security policy.
Every connected app has a setting that controls which users can access it. By default, this is often open to everyone, but you can restrict it to admins or pre-approved users only.
If the app is disconnecting for specific people, check the permitted users list first. Add anyone missing or widen the setting if broader access fits your security needs.
When an app installation fails, Salesforce still lists it under connected apps OAuth usage, even though setup never finished. This causes confusion later, since the app looks installed but is not.
To resolve it:
Once the install finishes, the app moves to your managed connected apps list, where you can edit its settings directly.
The last used date on a connected app tells you whether it stopped working entirely or is just having an occasional sync error.
You can find this detail on the connected user's profile. It is the fastest way to tell a full outage from a temporary glitch.
If you have worked through every step above and apps are still disconnecting, the cause may sit deeper in your Salesforce configuration or API setup. A Salesforce admin or certified partner can confirm whether the issue lives on Salesforce's side or with the app itself.
For the full range of connected app settings, see Salesforce's documentation on OAuth management.
Why did my Salesforce connected app suddenly stop working?
Most disconnections happen after a Salesforce security update tightens IP restrictions or authentication rules. A deactivated user or missing permission on the connected account causes the same result, so check user status first.
How do I fix an OAuth error in Salesforce?
Go to Setup, find the connected app, and check its IP restriction settings. Selecting "Relax IP Restrictions" resolves most OAuth errors tied to a recent security update, though your IT team should confirm the change fits your security policy.
What does the last used date on a connected app tell me?
An old last used date means the app has genuinely disconnected. A recent date means the app is still running, and the issue is likely a temporary sync error rather than a full outage.
Why does a failed app installation still show up in Salesforce?
Salesforce logs the app under connected apps OAuth usage as soon as installation starts, even if it never completes. Find it there, check for usage restrictions, and use "Load Actions" to finish the setup.
When should I contact a Salesforce partner instead of troubleshooting myself?
If you have checked user status, permissions, IP restrictions, and installation status, and the app is still disconnecting, the issue likely needs custom configuration or API-level changes that a certified partner can diagnose faster.
Need hands-on help fixing a Salesforce integration? Talk to Concept's Salesforce consulting team.