Skip to main content

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.

CodeStatusWhat it really meansFix
unauthenticated401No valid session or key.Sign in again, or check the Authorization: Bearer header.
forbidden403You can see the object but may not do this.Find the permission in Permissions and ask for a group that grants it.
not_found404It 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​

CodeStatusWhat it meansFix
interactive_only403This 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.
escalation403A grant would give more than you hold.Ask someone who holds that permission on that organization.
last_admin409The Administrators group must keep at least one active member.Add another administrator first.
cannot_modify_self409You cannot do this to yourself.Ask another administrator.
built_in409Built-in roles and groups keep their definition, and the root organization cannot be deleted.Create a custom role or group instead.
in_use409A group still uses this role.Move those groups to another role, then delete it.
org_not_empty409The organization still holds something.Move its contents and child organizations out first.
invalid_parent400You tried to move an organization somewhere it cannot go, or to move the root.Pick a parent outside its own branch.
already_member409That person is already a member.Add them to a group instead.
already_invited409That person has an invite.Resend the existing invite.
invite_domain_mismatch422The 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_domain409Your 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_session409This is your current session.Sign out instead.

Sign-in​

CodeStatusWhat it meansFix
invalid_credentials401These credentials do not match an account.Check the email and password.
sign_in_redirect400Sign-in happens through your identity provider.Use the URL from GET /api/v1/auth/config.
invalid_ott400The sign-in link expired, or you spent more than 15 minutes on the welcome screen.Sign in again.
email_unverified403Your 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_domain403This 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_up403Your 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_allowed422Your 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_claimed409Someone from your company created its organization first. The welcome screen shows Ask for an invite.Ask one of its administrators to invite you.
upstream502The 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.

ReasonFix
CredentialsCheck the token, its scopes and the account, then test again.
UnreachableCheck the server URL and that Dwaar can reach it, then test again.
TimeoutThe provider did not answer in time. Try again.
CodeStatusWhat it meansFix
not_connectable422This provider cannot be connected yet.See Planned integrations.
connection_test_failed422The test must pass before Dwaar saves the change.Fix the values and test again.
install_expired410A GitHub App install was started more than 30 minutes ago, by someone else, or has already finished.Start again from Add connection.
not_installer403The 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_credentials409The provider rejected the credentials.Replace the credential on the Connection tab.
connection_error409The connection is in an error state.Open the connection and run Test connection.
discovery_in_progress409A discovery of this connection is already queued or running.Wait for it to finish, or cancel it.
upstream_error502Dwaar 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​

CodeStatusWhat it meansFix
not_scannable409There is nothing to scan.Repositories and images can be rescanned. Other kinds get a one-time scan, and packages get none.
ref_limit409Too many tracked refs. At most 5 non-default refs can be on at once.Remove or exclude one first.
unknown_scanner400That scanner does not exist.Pick one from Scan Center.
unknown_version400That scanner has no such version.Pick a listed version.
conflict409The 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​

CodeStatusWhat it meansFix
ai_disabled409Your tenant turned Dwaar AI off.Ask an administrator to check Dwaar AI settings.
ai_not_configured409Dwaar AI is not set up.Ask an administrator to check the settings.
ai_tier_unavailable409That tier cannot run now.Use the other tier.
ai_budget_reached409The AI budget was reached.Wait until next month or ask an administrator.
ai_scope_empty409There is nothing in scope to read.Widen your filter.
ai_context_too_large413The request is too large.Narrow your filter.
ai_rate_limited429Too many requests.Wait, then try again.
ai_upstream_failed502The model call failed.Try again.

Query​

CodeStatusWhat it meansFix
invalid_query400The 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_busy429Too many queries are running, or too many questions were asked in the last minute.Wait a moment, then try again.
query_result_too_large413The result is over 5 MB. It is refused, not cut short.Ask for fewer rows or fields.
query_timeout504The 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​

CodeStatusWhat it meansFix
validation400A value in the request is wrong.Read the message, which names the problem.
invalid422The request was understood and refused.Read the message.
internal_error500Something went wrong on Dwaar's side.Try again. If it keeps failing, report the request id.