Troubleshooting
Troubleshoot Missing Data and Empty States
Most empty states come from filters, scope, role, or plan rather than missing data, so confirm those before escalating.
Updated June 5, 2026
Start with scope
Empty states usually mean one of three things: the data does not exist, the current filter hides it, or your role or plan cannot access it. Clear filters and confirm the facility first. Check the facility filter, date filter, saved view, status or priority filter, and search query.
Check the source workflow
If assets are missing, check import status, duplicate resolution, retired records, and facility assignment. If work orders are missing, check status, assignee, due date, and saved view. If analytics is empty, confirm there is enough completed or active history for the period.
Common empty-state causes
- New workspace with no seeded records.
- Facility filter set too narrowly.
- Imported rows skipped or excluded.
- Records assigned to another facility.
- Completed work hidden by status filters.
- Role does not allow the page, or the feature is not in the plan.
- Date range excludes the activity.
When to escalate
Escalate when a known record cannot be found after clearing filters, when multiple users see different results for the same scope, when a save succeeded but the record never appears, or when a drill-down and summary card disagree. Include the page URL, what you expected, what you saw, the facility or record involved, and a screenshot.
Still need help?
Reach out for broken behavior, account-specific help, or billing questions.