Troubleshooting
When something does not behave as expected, start with the simplest checks first.
Common checks
A job will not start
- confirm the correct run mode is not already active
- confirm the assigned runner or runner pool is available
- confirm the tenant still has allowance for a live run
A run looks stalled
- review the latest status and logs
- compare current progress with average progress
- confirm the source and target Storage Repositories are still reachable
A delta run falls back to sync
- confirm the job has a successful full-tree baseline
- review the run detail delta planning section for fallback scope reasons
- confirm the source and target paths still match the intended job scope
- run a scan if you need an independent reconciliation check
Local change-feed events are not picked up
- confirm the assigned dedicated runner is online
- run preflight and review the integrated smoke-test result
- confirm the watcher state is monitoring and the cursor status is ready
- check whether a full-tree baseline reset happened recently
- use ordinary tree sync until the runner reports trusted watcher state again
A scan result is confusing
- check which thresholds are currently active
- confirm whether the issue came from a stale scan or a fresh scan
- re-scan after remediation if you need updated findings
Escalation path
If the issue is not clear from the User Interface, collect:
- the job or run identifier
- the current status
- the affected Storage Repository type
- the exact operation you attempted