Troubleshoot setup and evidence
Identify the failing stage before retrying installation, sign-in, provider checks or background evidence jobs.
Setup link or deployment
Request a fresh link if the email link expired or was used. Check the edition, order eligibility and available release on the setup page.
For a failed installation, retain the original job and resource names. Return to that setup session and contact support; do not delete resources or create another installation.
Sign-in
Restart an expired challenge and check the authenticator's time. Ask an administrator to verify suspension, role and auditor expiry. A managed deployment intercepted by an Access login gate needs an operator to review its authentication mode.
Integration checks
- 401/403: verify the dedicated credential, required scopes, selected account and vendor entitlement.
- Missing resources: compare the configured production scope with the actual systems.
- Needs review/skipped: inspect the reason; unavailable API data is not a pass.
- Stale result: run a fresh check after source or scope changes.
- Queued work: check queue consumers, schedules and dead-letter handling before repeatedly enqueueing jobs.
Escalate
Send the release, edition, affected stage, timestamps, sanitized error and request/job identifiers to support. Exclude passwords, API keys, setup tokens, private email links and raw customer evidence.
See evidence checks and test alerts.