Troubleshooting
Something failed and you have an error code in front of you. Good news: the code is stable and precise. Find it below.
Every API error has the same shape: an error code, a message and usually a requestId. Keep the request id. It connects what you saw to the audit log, which also records every refused request.
Start here: is it access, or is it missing?
These two look similar and need different fixes.
| Code | Status | What it really means | Fix |
|---|---|---|---|
unauthenticated | 401 | No valid session or key. | Sign in again, or check the Authorization: Bearer header. |
forbidden | 403 | You can see the object but may not do this. | Find the permission in Permissions and ask for a group that grants it. |
not_found | 404 | It does not exist for you. That includes objects in another tenant and objects on organizations where you hold no permission. | Do not assume it is gone. Check your access first. |
Access and keys
| Code | Status | What it means | Fix |
|---|---|---|---|
interactive_only | 403 | This action needs a signed-in user, not an API key. | Do it in the console. Creating API keys and starting Dwaar AI runs work this way. |
escalation | 403 | A grant would give more than you hold. | Ask someone who holds that permission on that organization. |
last_admin | 409 | The Administrators group must keep at least one active member. | Add another administrator first. |
cannot_modify_self | 409 | You cannot do this to yourself. | Ask another administrator. |
built_in | 409 | Built-in roles and groups keep their definition, and the root organization cannot be deleted. | Create a custom role or group instead. |
in_use | 409 | A group still uses this role. | Move those groups to another role, then delete it. |
org_not_empty | 409 | The organization still holds something. | Move its contents and child organizations out first. |
invalid_parent | 400 | You tried to move an organization somewhere it cannot go, or to move the root. | Pick a parent outside its own branch. |
already_member | 409 | That person is already a member. | Add them to a group instead. |
already_invited | 409 | That person has an invite. | Resend the existing invite. |
invite_domain_mismatch | 422 | The address is not at your tenant's email domain. Invites only go to your own company's addresses. | Invite them at their address on your company's domain. |
tenant_without_domain | 409 | Your tenant has no company email domain yet, so it cannot invite anyone. | Contact Dwaar support to set it, then sign out and sign in again. |
current_session | 409 | This is your current session. | Sign out instead. |
Sign-in
| Code | Status | What it means | Fix |
|---|---|---|---|
invalid_credentials | 401 | These credentials do not match an account. | Check the email and password. |
sign_in_redirect | 400 | Sign-in happens through your identity provider. | Use the URL from GET /api/v1/auth/config. |
invalid_ott | 400 | The sign-in link expired, or you spent more than 15 minutes on the welcome screen. | Sign in again. |
email_unverified | 403 | Your email address is not verified. Creating or choosing an organization, and accepting an invite, all need a verified one. | Verify your email address, then sign in again. |
wrong_domain | 403 | This console is set up for one company, and your account belongs to another company's tenant. | Sign in with your account at the company this console serves. |
org_not_set_up | 403 | Your organization already uses Dwaar, but its administrator has not opened the console yet. | Ask an administrator of your organization to sign in to the console first, then to invite you. |
domain_not_allowed | 422 | Your address cannot create an organization, usually because it is a personal or throwaway one such as Gmail. The welcome screen shows Use your organization email. | Sign in with your work email. |
domain_claimed | 409 | Someone from your company created its organization first. The welcome screen shows Ask for an invite. | Ask one of its administrators to invite you. |
upstream | 502 | The sign-in service did not complete a sign-in, an invite or a removal. | Try again in a moment. If it keeps failing, report the request id. |
Landed on a welcome screen instead of the console? You have no tenant here yet, or more than one, and the screen says what to do next. Quickstart explains each one.
Integrations
When Test connection fails, it gives a reason.
| Reason | Fix |
|---|---|
| Credentials | Check the token, its scopes and the account, then test again. |
| Unreachable | Check the server URL and that Dwaar can reach it, then test again. |
| Timeout | The provider did not answer in time. Try again. |
| Code | Status | What it means | Fix |
|---|---|---|---|
not_connectable | 422 | This provider cannot be connected yet. | See Planned integrations. |
connection_test_failed | 422 | The test must pass before Dwaar saves the change. | Fix the values and test again. |
install_expired | 410 | A GitHub App install was started more than 30 minutes ago, by someone else, or has already finished. | Start again from Add connection. |
not_installer | 403 | The GitHub App installation is not yours, or you are not an owner of its organization. | Ask an owner of that organization to connect it. |
provider_credentials | 409 | The provider rejected the credentials. | Replace the credential on the Connection tab. |
connection_error | 409 | The connection is in an error state. | Open the connection and run Test connection. |
discovery_in_progress | 409 | A discovery of this connection is already queued or running. | Wait for it to finish, or cancel it. |
upstream_error | 502 | Dwaar could not reach the provider or a service it depends on. | Try again. If it keeps failing, report the request id. |
A connected account with an empty discovery list means the account is reachable but holds nothing the credentials can read. Check the token's scope, and any include or exclude globs.
Scans and resources
| Code | Status | What it means | Fix |
|---|---|---|---|
not_scannable | 409 | There is nothing to scan. | Repositories and images can be rescanned. Other kinds get a one-time scan, and packages get none. |
ref_limit | 409 | Too many tracked refs. At most 5 non-default refs can be on at once. | Remove or exclude one first. |
unknown_scanner | 400 | That scanner does not exist. | Pick one from Scan Center. |
unknown_version | 400 | That scanner has no such version. | Pick a listed version. |
conflict | 409 | The run has already finished, or the request clashes with the current state. | Reload, then try again. |
A queued scan is not moving? Open it in Scan Center. It says what it is waiting for, usually that your tenant's running scans are at the cap.
Findings count looks low? Ignored findings and older versions are left out by default. Check the filter, and read GraphQL if you are querying the API.
Nothing is being scanned? Check that at least one trigger is on in the connection's Scanning tab. With both off, discovery only lists resources. See Integrations.
Dwaar AI
| Code | Status | What it means | Fix |
|---|---|---|---|
ai_disabled | 409 | Your tenant turned Dwaar AI off. | Ask an administrator to check Dwaar AI settings. |
ai_not_configured | 409 | Dwaar AI is not set up. | Ask an administrator to check the settings. |
ai_tier_unavailable | 409 | That tier cannot run now. | Use the other tier. |
ai_budget_reached | 409 | The AI budget was reached. | Wait until next month or ask an administrator. |
ai_scope_empty | 409 | There is nothing in scope to read. | Widen your filter. |
ai_context_too_large | 413 | The request is too large. | Narrow your filter. |
ai_rate_limited | 429 | Too many requests. | Wait, then try again. |
ai_upstream_failed | 502 | The model call failed. | Try again. |
Query
| Code | Status | What it means | Fix |
|---|---|---|---|
invalid_query | 400 | The query cannot run here: a field the schema does not have, more than one operation, or over the depth or complexity limit. | Read the message. The Query editor shows the same problem by line and column, for free. |
query_busy | 429 | Too many queries are running, or too many questions were asked in the last minute. | Wait a moment, then try again. |
query_result_too_large | 413 | The result is over 5 MB. It is refused, not cut short. | Ask for fewer rows or fields. |
query_timeout | 504 | The query took longer than 15 seconds. It costs nothing. | Narrow it with a filter or ask for fewer rows. |
Building a query uses the same ai_ codes as above, so ai_disabled means asking is off while a query you write still runs.
The answer looks wrong? Read Understood as and the query. Ignored findings and older versions are left out unless the query asks for them, as in GraphQL.
Validation and server errors
| Code | Status | What it means | Fix |
|---|---|---|---|
validation | 400 | A value in the request is wrong. | Read the message, which names the problem. |
invalid | 422 | The request was understood and refused. | Read the message. |
internal_error | 500 | Something went wrong on Dwaar's side. | Try again. If it keeps failing, report the request id. |