Couldn't reach MaintainX
MaintainX API 429: {"error":"Rate limit exceeded"}
Average completion time
Month to date · 15 days
For every work order marked DONE inside this range, we compute the time from
Click the pencil icon on any row to correct a stuck timestamp or reclassify a WO — overrides live in this browser and are managed from the Settings tab.
createdAt → completedAt and group by priority. Recurring / preventive work orders are excluded— site PMs and their scheduled instances don't count toward the averages. Currently ON_HOLD work orders are also excluded and shown on their own card below.Click the pencil icon on any row to correct a stuck timestamp or reclassify a WO — overrides live in this browser and are managed from the Settings tab.
High priority
—
avg over 0 completions
Median: —
Medium priority
—
avg over 0 completions
Median: —
Low priority
—
avg over 0 completions
Median: —
On hold
0
currently ON_HOLD
Avg time on hold: —
Longest: —
Completion time by priority
0 non-recurring work orders closed in-range. Median is the fair “typical” number — mean is skewed by long tails. p95 is the slowest 5% cutoff — treat it as “worst common case”. Adjusting a WO's timestamps in the Settings tab updates these numbers live.
No work orders were completed inside this range.
On hold
Currently on hold
Snapshot of everything in ON_HOLD right now, longest-held first. “Time on hold” is approximated from
now − updatedAt — MaintainX doesn't expose status transition history via REST, so this is exact when the last edit was the hold transition, and an underestimate otherwise. Use the pencil to correct a WO that's stuck ON_HOLD in MaintainX but was actually completed.Nothing is on hold right now — clean queue.
Data pulled live from MaintainX · refreshed Sep 15, 2026, 6:27 AM · Range: 15 days.