Troubleshooting Superadmin
A problem looks global, but I am not sure
Check:
- whether the same symptom appears in more than one company
- whether the issue started after a platform-wide change
- whether tenant-local settings explain the problem first
Metrics show pressure, but the product still works
That usually means early platform stress, not yet a confirmed outage.
Check:
- queue and worker trend, not one isolated metric
- storage growth together with backlog indicators
- whether one subsystem or many are affected
A platform-wide change fixed one issue, but caused another
Typical causes:
- the change affected more scope than intended
- several defaults were changed together
- the effect belongs to permissions, workers, or company scoping rather than the edited form alone
AI or LLM settings look correct, but outcomes still seem wrong
Check:
- whether the user is in the right admin or superadmin area
- whether sensitive resources such as payloads or custom headers remain restricted
- whether the issue belongs to data scope rather than to model connectivity
When to use the technical docs
Switch to /sysdocs when you need:
- exact route and module boundaries
- role and permission enforcement details
- value and lifecycle states from the underlying models
- AI, worker, or platform operating internals