You are here:
Optimize and Troubleshoot Automation in Salesforce Authenticator
If Salesforce Authenticator isn’t automating your activity as expected, review our troubleshooting suggestions.
Required Editions
| Available in: all editions |
Optimize your device settings.
Your device settings can prevent the app from successfully automating requests. To optimize automation performance, use these device settings.
For iOS users:
- Location Services: Always
- Background App Refresh: On
For Android users:
- Location Permissions: Allow all the time and Use precise location
- Background Data: On
- Battery Saver Mode: Select Authenticator so the app can still operate in the background
Find out why a request wasn’t automated.
Use the Recent Activity tool to determine why a request wasn’t automated.
- In your Connected Accounts list, tap the arrow icon (
) to view
an account’s details. - In the Recent Activity section, tap View All.
- Tap the request that you manually responded to.
- Scan the User Action page to find the issue.
Here are two common scenarios where the request can't be automated.
Authenticator doesn’t recognize the client (1). To automate this request in the future, approve the request with the new client.
The service blocked automation for the request (1). The service can temporarily block automation if it notices unusual activity or a potential security risk. To find out why automation was blocked for a request, contact your Salesforce admin.
Review the order of factors in an automated verification.
To understand why some requests aren’t automated, it’s helpful to review the organization of factors in an automated verification. Authenticator detects the action, location, and client in this order.
- Action
- Location
- Client
When you save an automated verification, the app remembers each factor in the context of the factor before it. The client is trusted only at the detected location, and the location is trusted only for the detected action.
Compare the Incoming Request with Automation #1 and Automation #2.
| Factor | Automation #1 | Automation #2 | Incoming Request |
|---|---|---|---|
| Action | Log In | Log In | Log In |
| Location | Office | Home | Home |
| Client | Chrome Desktop Browser | Salesforce Mobile App | Chrome Desktop Browser |
The Chrome Desktop Browser client is trusted only at the Office location (Automation #1), and the only trusted client at the Home location is the Salesforce Mobile App (Automation #2). Because neither automated verification captures the Chrome Desktop Browser client at the Home location, the Incoming Request can’t be automated.
You can automate more of your activity over time by saving automated verifications for different sets of factors.

