Skip to content
ROKKS Docs
DRAFTEnglish end user manual · web beta f7b7740e7371 · Android beta ed5d9494be9eDownload PDF

Troubleshooting

Overview

Section titled “Overview”

Troubleshooting in Rokks starts with scope and evidence. Most issues can be narrowed by checking environment, tenant, job status, source health, and the affected route family.

How it works

Section titled “How it works”

The UI shows symptoms, but operations pages show causes. A missing dashboard may be a scope issue. A blank widget may be a query or metadata issue. A stale source may be a failed sync job. A notification issue may be an alert evaluation or external channel issue.

MOCKUPSource-derived illustration — not a captured product state
Source-derived Query Optimizer mockup
Query Optimizer illustration showing engine state and the source-defined empty findings state.Source baseline: beta f7b7740e

Step-by-step

Section titled “Step-by-step”
  1. Capture the user action and time.
  2. Confirm environment and tenant.
  3. Check whether the source or dashboard exists in that scope.
  4. Open the Job Queue for related failures.
  5. Check Monitoring and Service Stack.
  6. Read the most specific error message.
  7. Fix the upstream cause before rerunning the workflow.

Common mistakes

Section titled “Common mistakes”

Do not refresh repeatedly without checking job state. That can hide the original failure.

Do not widen permissions to “fix” missing data until scope and ownership have been confirmed.

Section titled “Related”