How to Retry a Failed Scan
Scans can occasionally fail due to connectivity issues, API limits, or temporary Salesforce errors. This guide explains how to find and retry failed scans.
Prerequisites
- You must have the Aprity_Admin permission set assigned to retry scans.
- The scan must be in a Failed status.
Steps
- Open the aprity app in Salesforce.
- Navigate to the Analyses tab.
- Locate the failed scan in the list. Failed scans display a red status badge.
- Click on the failed scan to open its detail view.
- Click the Retry button in the action bar.
- aprity will re-queue the scan from the last successful phase.
info
Only users with the Aprity_Admin permission set can retry scans. If you do not see the Retry button, contact your Salesforce administrator.
Common Reasons for Failure
| Reason | Description |
|---|---|
| API Limit Exceeded | Your Salesforce org hit its daily API call limit. Wait for the limit to reset (midnight UTC) and retry. |
| Authentication Expired | The JWT Bearer token could not be refreshed. Check your Named Credentials in Setup. |
| Timeout | A metadata extraction step took too long. This can happen with very large orgs. Retry usually resolves it. |
| Temporary Service Error | A transient issue with aprity's backend. Retry after a few minutes. |
What Happens on Retry
aprity resumes the scan from the last successful workflow phase rather than starting from scratch. For example, if metadata extraction succeeded but analysis failed, the retry skips extraction and goes directly to analysis.
tip
If a scan fails repeatedly on the same phase, check the Salesforce debug logs for API errors and verify your Named Credentials are correctly configured.