Troubleshooting and Known Exceptions¶
This page captures live-capture findings that are useful to operators, trainers, and reviewers. It separates validated user flows from routes that should not yet be presented as normal operating procedures.
1. Known Route Exceptions Observed During Live Capture¶
The following routes returned frontend runtime errors during the documented live session:
/routes/route-devices/settings/server
Treat these as defects, not as supported operator flows.
2. When to Treat a Page as Slow Rather Than Broken¶
Use patience first when the page is known to have asynchronous behavior.
| Area | Expected behavior |
|---|---|
| Reports | Can take substantially longer than normal pages before the embedded analytics frame finishes loading |
| Large data tables | May need additional time after filters change or on initial load |
| Map-based views | Can appear incomplete until tiles and location layers finish loading |
3. When to Escalate Immediately¶
Escalate promptly when any of the following happens:
- login succeeds but protected pages do not load
- multiple modules show blank pages for several users
- reports never render after the normal long wait window
- row actions repeatedly fail or route to broken pages
- map-based screens fail consistently rather than intermittently
4. First Checks Before Escalation¶
- Refresh the page once and confirm the issue persists.
- Confirm the user still has a valid authenticated session.
- Reproduce the issue in the same module using a second record if possible.
- Check whether the issue affects only one route or an entire module.
- Capture the exact route and visible error state before escalating.
5. Relationship to Other User-Guide Pages¶
- Use the task pages in this user-guide section for validated operator flows.
- Use Portal Screenshot Reference when you need route-by-route UI-state notes.
- Use Portal Annotated Training Guide when training requires labeled callouts on the interface.