Reference / 5 MIN READ
Troubleshoot common problems
Resolve runner, identity, inventory, and policy-check issues without exposing credentials.
The workspace cannot reach the runner
For Local, confirm the launcher is still running and open http://127.0.0.1:5127/app/. If port 5127 is already in use, stop the old installation before starting a new one. A hosted product website does not install or start a runner on your laptop.
For Self-hosted, ask your administrator to check HTTPS, proxy configuration, application health, and database connectivity. Do not point a hosted frontend at a developer’s laptop.
Azure is disconnected or inventory is empty
In Local, verify az account show uses the intended tenant and that resource-graph is installed. Sign in again if required. In hosted mode, open Account settings and use Connect Azure or Reconnect Azure.
Check subscription filters and your Azure permissions. Refresh after a configuration change, then allow time for Resource Graph updates. Read incomplete-data warnings; a partial result is not proof that a resource is absent.
Microsoft sign-in fails
A hosted administrator should check the tenant allowlist, app registration, exact /signin-oidc redirect URI, consent, application assignment, and Conditional Access. Use the public HTTPS hostname configured for that installation. Never send anyone your password, access token, or session cookie.
Policy Validation is inconclusive
Open the run’s evidence and compare Azure evaluation timestamps with the plan’s maximum age. Check assessed-resource coverage, expected resource IDs, unresolved states, permissions, and query-limit messages. Wait for Azure to publish fresh evaluations before rerunning when appropriate.
Increasing freshness tolerance changes what the plan accepts; it does not refresh Azure’s data. Papliba does not trigger a scan or test enforcement.
A drawing or workspace is missing
Infradraw is saved in the current browser profile, not the hosted database. Clearing site data or changing browsers can remove access to a draft. Hosted workspaces are private per user; verify that you signed in with the intended identity. Local workspace data is not automatically uploaded to hosted editions.
Information to share with your administrator
- Installation mode, application version, operating system, and the time of the problem.
- The section and exact action that failed, plus a redacted error message.
- Whether the issue affects one user or multiple users. Remove tenant/resource identifiers if your organization treats them as sensitive.