Troubleshooting
The one-time sign-in code never arrives
- Confirm you entered your organization email, not a personal address.
- Check spam and quarantined mail.
- Request a new code from the sign-in page.
- If two-factor authentication is enabled, have your TOTP code ready.
- Contact hello@frigga.cloud if no code arrives.
Onboarding will not let me continue
- Confirm the company profile is reviewed and confirmed.
- Confirm at least one workspace exists.
- Confirm at least one environment exists.
- Confirm at least one repository is mapped to a workspace.
- Confirm a cloud connection shows Connected.
A cloud connection shows Validation failed
- Confirm the credentials are read-only and still active.
- Confirm the connection method matches the provider — access key or assume role for AWS, service account key for GCP, app registration for Azure.
- Re-enter the credentials; saved values are masked and cannot be inspected.
- Retry validation and check the state moves to Connected.
The scan finished but resources are missing
- Open Scan results and check per-service status.
- Look for missing permissions, failures or throttling.
- Confirm the resource type is one Vörr indexes.
- Re-run the scan after correcting access.
- Do not treat the empty result as a zero until the relevant services completed.
A repository is not appearing in Vörr
- Confirm the Git provider authorization completed.
- Confirm the repository was selected during connection.
- Confirm the repository is mapped to a workspace.
- Wait for indexing to finish, then refresh.
- Contact support if the repository should already be available.
A connector fails to authenticate
- Confirm the token or service account was created with the documented permissions.
- For Jenkins, use an API token rather than SSO web credentials.
- For Grafana, use a Viewer service-account token.
- Confirm the endpoint URL and authentication method.
- Re-test the connection.
An answer names the wrong service
- Open the service map and check how the name was matched.
- Add an explicit mapping between the Vörr service and its name in the other tool.
- Re-ask the question and confirm the match is reported as explicit.
- Map the remaining important services — it is the fastest way to improve answer quality.
MCP authorization fails or expires
- Confirm the endpoint ends in /api/v1/mcp.
- Restart the connection from the AI assistant if the consent request is stale.
- Sign in again on the Vörr consent screen and choose Allow.
- Confirm your AI plan supports custom connectors.
- Reconnect to refresh the authorization.
The assistant says nothing is connected
- Confirm your organization has completed onboarding.
- Confirm at least one repository, cloud account or connector exists in Vörr.
- Confirm you authorized with the same account and organization.
- Ask a question naming a service you know is connected.