Skip to content

Troubleshooting

Troubleshoot Work-Order Counts and Filters

Check filters and scope before assuming data is broken, understand why counts change, and escalate when cards and drill-downs disagree.

Updated June 5, 2026

Start with the visible filters

When counts look wrong, verify scope before assuming data is broken. Clear filters, confirm facility, reset search, and check status. The filters that most often explain surprises are:

  • facility
  • status
  • priority
  • assignee
  • date range
  • saved view
  • search text
  • completed versus open work
  • board truncation or pagination

Overdue is based on the active SLA or due target for an open or in-progress work order; a completed work order should not behave like active overdue work. Use the list or board, not just the card, to validate what a number means.

Why counts change

Counts may change after work is completed, due dates are rescheduled, an import updates asset or facility context, a saved view is edited, or a PM run generates new work. A change is not always a problem; the question is whether the underlying records support it.

When to escalate

Escalate if a card and its drill-down disagree under the same filters, completed work still appears overdue, a saved view returns unstable results, or users see different counts for the same role and scope. Include the filter state, page URL, expected and actual counts, and example work-order IDs.

Still need help?

Reach out for broken behavior, account-specific help, or billing questions.

Contact support
Book a demo