Error Dictionary

If a term is unfamiliar, open the Glossary.

This page gives plain-language explanations for the most common workspace-facing errors in Dralvia and exactly what to do next.

Who this is for

This guide is for workspace owners, workspace admins, and security operators who need fast, repeatable fixes when UI/API actions fail.

Role-based start here

• Workspace Owner: Start with Before you start, then complete Step-by-step and Known limits and rate limits.
• Workspace Admin: Focus on Step-by-step, What each button does, and API and automation.
• Security Analyst: Start at Day-2 operations and Troubleshooting, then use API error quick reference.
• Integrator/Engineer: Start at API and automation, then validate with Step-by-step and FAQ.

Before you start

1. Confirm you are signed into the correct workspace account.
2. Confirm your role has permission for the action you are trying to run.
3. Keep your browser devtools/network tab available for exact error text and HTTP code.

Step-by-step

1. Find the exact error text or HTTP code.
2. Match it to the matrix in this page.
3. Execute the listed fix steps in order.
4. Retry once.
5. If unresolved, use the escalation template in this page.

Day-2 operations

1. Track recurring errors by feature each week.
2. Convert repeated fixes into internal SOP notes.
3. Escalate trend-level failures (for example repeated 500 or sustained 429 on normal workloads).

What each button does

• Refresh: reloads latest state from backend.
• Save: persists workspace-scoped configuration changes.
• Run/Probe/Validate: executes a health or verification check.
• Verify: performs integrity/consistency validation.
• Download: retrieves artifacts (bundle/checksum/signature/report).

If a button is disabled, check permission scope, required fields, and workspace entitlement first.

Self-check playbook

Use this 5-step isolation flow before escalating:

1. Configuration: confirm required inputs are present and formatted correctly.
2. Permission: confirm your role can perform the action (401/403 usually indicates authz/authn mismatch).
3. License/feature: confirm the feature is enabled for your workspace plan and module toggles.
4. Quota/rate limit: check for 429 responses and cooldown windows.
5. Service health: if you see 5xx, retry once after 30-60 seconds and capture exact error text.

If still failing, escalate with workspace ID, UTC timestamp, route, action, payload shape (no secrets), and screenshot/error response.

Troubleshooting

Use this order:

1. Session/auth check.
2. Workspace context check.
3. Input/config check.
4. Quota/license check.
5. Service health/transient retry.

API error quick reference

Use this matrix when a UI action fails with an HTTP/API error.

Error	Meaning	What to do now
401 Unauthorized	Session token is missing/expired or request is not authenticated.	Sign out/in, refresh once, then retry. Confirm your session is active in the correct workspace.
403 Forbidden	You are authenticated but your role is not allowed to perform this action.	Confirm your role includes the required permission for this action. Ask workspace admin to grant access.
404 Not Found	The route/resource does not exist in current workspace context (or feature not enabled).	Confirm URL/route, workspace context, and feature availability. Refresh and retry; if persistent, capture timestamp and route and contact support.
429 Too Many Requests	Rate limit/quota window was exceeded.	Wait for cooldown/reset window, retry once, then reduce burst traffic/backoff if automated.
500 Internal Server Error	Backend failed unexpectedly while processing the request.	Retry after 30-60 seconds. If still failing, escalate with workspace ID, UTC time, route, action, and full error text.

Top recurring support issues (route-specific)

Use this matrix for the most frequent issues reported by workspace operators.

Route / area	What users usually see	Most likely cause	Fastest fix
#/ Scanner	Scan failed or immediate risk 0 with no real result	Domain input invalid, stale session, or workspace context mismatch	Re-enter domain (for example test.ro), sign out/in once, then rerun scan and confirm network call response body.
#/swg-policy	Unable to load dry-run events	Backend 500 or stale policy/event schema mismatch	Refresh once, retry in 30-60s, then capture failing request path and timestamp for escalation if persistent.
#/edr-console	Failed to load hosts	Sensor not enrolled, host inventory query failure, or missing workspace state	Confirm at least one sensor reports telemetry, then refresh host inventory and verify API key/session validity.
#/identity-risk	Alerts not updating	Event source not sending required identity fields	Validate sender payload includes workspace/user/session/IP/event fields, then post one controlled test event.
#/trust-verify	pack_not_found	Wrong hash/index or entry from a different workspace	Load latest witness first, then verify using the exact pack hash/transparency index from current workspace output.
#/trust-verify	index_out_of_range	Transparency index doesn’t exist in current log window	Refresh log, pick a valid recent entry, and retry verify.
#/risk-economics	Unable to save profile (HTTP 404)	Route mismatch or missing backend endpoint in current deployment	Refresh, verify current release version, then test API profile endpoint directly and escalate if 404 persists.
#/autonomous-readiness	Something went wrong / Unable to load tenant readiness	Readiness API error, auth drift, or module data missing	Hard refresh, re-authenticate, then run probe once and capture request/response details if still failing.
Any dashboard	Unauthorized: missing API key	Session/API key missing for workspace-scoped request	Re-authenticate, confirm workspace context, and verify API key is present and active for the environment.
Any workflow	Repeated 429 warnings	Burst traffic exceeded rate limits	Wait for cooldown, retry once, then add client-side backoff/jitter for automation paths.

API and automation

If you automate workflows:

• Keep requests workspace-scoped and authenticated.
• Use retry/backoff for 429/5xx cases.
• Avoid blind retry loops for 403/404.
• Reconfirm expected outcome in UI after automation runs.

Next best actions

After finishing this page, continue with related workflows so your workspace setup stays end-to-end complete:

• EDR response and host actions
• Web Access Protection and dry-run events
• Identity risk and OAuth response
• EvidencePack verification and transparency log
• Risk economics and plan recommendation

FAQ

Q: Save succeeds but I still see the same issue.
A: Refresh and verify the change was applied in the current workspace context.

Q: Why do I keep seeing missing API key or unauthorized?
A: Check both workspace API key validity and active browser session token.

Q: When should I escalate immediately?
A: Repeated 500s on core workflows, sustained 429 under normal usage, or permission failures that block security response.

Escalation template

Send this in one message to reduce back-and-forth:

• Workspace ID:
• User role:
• Route/page:
• Action attempted:
• Exact error text:
• UTC timestamp:
• Browser + OS:
• Relevant request path (if known):
• Screenshot (optional but recommended):

Next steps

1. Bookmark this page for operators.
2. Link your internal SOP to this dictionary.
3. If recurring errors are not listed here, request a dictionary update through support.

Known limits and rate limits

These limits can vary by plan and feature, but behavior is consistent:

• Burst traffic can trigger 429 Too Many Requests.
• Workspace quotas apply per feature/module and reset on configured windows.
• Repeated retries without backoff can extend recovery time during saturation.

Recommended operator behavior:

1. Retry once after cooldown for 429 responses.
2. Use exponential backoff in automation.
3. Monitor usage/quota dashboards for sustained high utilization.
4. Request quota review when normal workload regularly approaches limits.