Troubleshooting
Safe next steps for failed audits, missing permissions, stale costs, PDF export failures, and empty reports.
On this page
No findings
Check your selected provider and connections, then open the latest audit and read its outcome and coverage limits. No findings can mean no supported condition was detected in the collected scope.
It can also mean the audit has not finished or required evidence was unavailable. Check cost ingestion separately if the missing result is a financial total.
Connection validation failed
Open the connection's safe failure summary and identify which check failed. For Azure, confirm the tenant, application and selected subscription, secret expiry and role assignments.
For AWS, confirm the role's account, trusted principal and workspace-generated external ID. If role entry succeeds but cost access fails, fix the cost permission or provider configuration instead of replacing the role with broad write access.
Revalidate after correcting the affected setting.
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.
What to include in a support request
Include the affected provider, displayed connection or audit identifier, time of the problem and safe status message. Explain what you expected and which check failed.
Omit client secrets, access keys, session tokens and raw provider responses. If you share a screenshot, remove unrelated account and resource details first.
Integration delivery failed
Review the delivery receipt and destination status. A preview does not send a message, and an accepted request does not prove someone read it.
Follow the displayed retry guidance; an uncertain outcome may prohibit resending to avoid duplicates. In-app read state is separate from external delivery.
Share the safe failure summary and support reference, never tokens, signing secrets, webhook payloads, or raw provider errors.
Identity or role access is limited
Sign in normally and confirm the active workspace. Ask its administrator to review your role and the capability's configured access.
A help page or shared review link cannot grant permission. If the issue remains, contact support with the affected page, connection or run reference, and displayed safe message.
Exclude private resource details unless support specifically needs them through an approved channel.
AI output has missing sources
Keep a draft out of approval when its required sources are missing. Inspect the underlying finding or report and resolve its evidence limitation first.
A new explanation cannot establish provider activity or financial attribution that the source records do not support. Preserve the unavailable or partial state when forwarding the issue to the reviewer.