Troubleshooting
Safe next steps for failed audits, missing permissions, stale costs, PDF export failures, and empty reports.
Implementation checklist
- 01Review pdf export failed before relying on this area.
- 02Review no findings before relying on this area.
- 03Review connection validation failed before relying on this area.
- 04Review costs are stale or missing before relying on this area.
- 05Review integration delivery failed before relying on this area.
- 06Review identity or role access is limited before relying on this area.
- 07Review ai output has missing sources before relying on this area.
PDF export failed
Retry the PDF export first. A PDF failure does not mean the audit failed. If the runtime cannot launch Chromium, run `pnpm pdf:smoke` in the deployment environment.
No findings
Confirm the connection has a completed audit, synced billing rows, inventory snapshots, and enabled provider capabilities.
Connection validation failed
Review the customer-safe failure category on the connection, compare the granted read scopes with the provider guide, then revalidate. Do not replace a least-privilege role with broad write access.
Costs are stale or missing
Check connection health, billing-export readiness, the most recent cost-sync state, native currency, and selected scope. A successful inventory audit does not prove billing ingestion succeeded.
Integration delivery failed
Review the delivery state, destination health, retry schedule, and dead-letter reason. Never paste signing secrets, tokens, webhook payloads, or raw provider errors into a support request.
Identity or role access is limited
Confirm the active Clerk organization, workspace role, plan entitlement, and Microsoft Entra readiness. Help content cannot grant a role or bypass server-side authorization.
AI output has missing sources
Treat the output as unavailable for approval. Refresh the underlying evidence or create a new draft only after the required sources are present.
Data sources and freshness
NextAction lifecycle