Troubleshooting
Common Review Problems
What to check first when a review does not start, does not finish, or returns unexpected scope.
What this page is for
This page helps you work backward from a review symptom to the most likely thing to check next.
When to use it
Use it when:
- a review is stuck
- a review failed
- the scope or output looks wrong
- you are not sure whether the problem is Azure access, queue execution, or report generation
How to diagnose it
The review stays queued
This usually points to execution rather than Azure access.
Check:
- the queue worker is running
- the queue backend is healthy
- jobs are being picked up at all
The review fails quickly
This often points to access problems.
Check:
- the saved connection still validates
- the token is still valid and for the right audience
- the subscriptions you expected are actually reachable
No subscriptions are found
This usually means either:
- the access really cannot see subscriptions
- the connection or token is not the one you thought you were using
The review completed but the report is not ready
This usually means the report generation step is still running. Check the report tab before assuming a failure.
The results look wrong
Before distrusting the findings, verify:
- the customer
- the auth path
- the subscriptions in scope
What to expect
Most review issues are easier to solve when you identify whether the problem belongs to execution, access, or scope first.
Common mistakes
- re-running the review repeatedly before diagnosing the actual failure
- treating queued state as proof of Azure access problems
- reading the findings before checking the scope