Analysis Stuck in Progress
An analysis reads your org's metadata, computes the dependencies, uses AI to write the documentation, checks it, and publishes a new version in the web portal. On a large org with a lot of automation this takes a while. A long analysis is not necessarily a stuck one.
Check whether it is progressing
In the aprity app in Salesforce, open Analyses and look at your analysis. The progress indicator updates while the analysis runs.
- The progress moves, even slowly: the analysis is running. Let it finish.
- The progress has not moved for a long time: some steps take longer than others (for example, the AI analysis of a large org). Wait a little longer before acting.
While an analysis runs, the web portal keeps showing the previous version. The new version appears once the analysis has published it.
Why an analysis can be slow
- Org size. The number of objects, fields, classes, flows and rules drives the duration.
- Temporary errors. aprity retries steps that fail for temporary reasons (network, Salesforce or AI service throttling). Retries add time but do not need any action from you.
- Interrupted processing. If processing is interrupted on the aprity side, the analysis picks up where it stopped. This can add some delay.
What to do
- Check status.salesforce.com for your instance. A Salesforce incident can slow or stop the metadata reading.
- If the progress has not moved for several hours, contact aprity support.
You cannot start a second analysis while the weekly limit is used (see Analysis Refused or Quota Reached), so a restart on your side is usually not possible. Support can check the analysis and restart it if needed.
When you contact support, include:
- The date and time the analysis started.
- The last progress you saw.
- Your Salesforce Org ID.