Why it matters
Not every machine run needs your attention, but some do — a machine left running over a weekend, a run someone entered by hand after the fact, or a worker's own fix to a stuck run. Reviewing these keeps your machine cost and utilization numbers honest.
How it works
FabWise flags a machine run for review when:
- The run's final duration is unusually long (more than a day) — usually a forgotten Stop tap.
- The run was entered manually by an admin rather than tapped live.
- A worker corrected the run's end time themselves (see below) — this always gets a look, even if the corrected number looks fine.
A flagged run stays flagged until you either correct it or acknowledge it as-is. If something about the run changes later — a correction, for instance — and it still meets a flag condition, it flags again automatically.
Where to find it
- Page: Admin — Machine Runs
- Path: Machines > (a machine) > Runs, or the Machine Runs list directly
- Who can see it: account owners, admins, and managers
What you'll see
The Machine Runs list
Every run, filterable by machine or by "needs review." A flagged run is visually called out.
A flagged run's detail
Shows the tapped times, who started it, which job it's attributed to, and why it's flagged.
Worker self-corrected runs
If a worker fixed a stuck run's end time themselves, the run shows their correction and is always flagged for your review — even a stuck run they fixed reasonably deserves a confirming look.
What to do
- If the run looks right: tap Acknowledge. This clears the flag and records that you reviewed it.
- If the times are wrong: correct the start and/or end time. This doesn't erase the original tapped times — it adds your correction on top, and FabWise always shows the corrected number going forward.
- If the run is attributed to the wrong job: re-assign it to the correct job from the same correction screen.
- If a run was never tapped at all (a machine ran but nobody started it in FabWise): use Add Manual Run to enter it by hand. Manual runs always start out flagged for review, so make sure someone double-checks it.
Common questions
Q: A worker fixed their own stuck run — do I still need to look at it?
A: Yes. Self-corrected runs always flag for your review, even if the fix looks right, because it's a worker asserting a time rather than a live tap.
Q: Can a worker correct anything besides the end time?
A: No. Workers can only fix a stale run's end time from Workstation. Everything else — start time, job attribution, manual entry — is admin-only.
Q: What if I correct a run and it's still flagged?
A: Check whether it still meets a flag condition (still over a day long, still manually entered). If the underlying reason is resolved, acknowledging clears it.
Q: Does acknowledging a run change any numbers?
A: No. Acknowledging only clears the review flag — it doesn't change the run's times, job, or cost.
Related
Last updated: 2026-07-23