Home/Answers/Breaks
ATLAS LAB / Breaks

Breaks Failed? Troubleshooting

When Breaks fails, troubleshoot in order: file/format, permission/lock, output settings, another tool.

Updated 2026-11-01About 3 minLocal test
Quick answer

When Breaks fails, troubleshoot in order: file/format, permission/lock, output settings, another tool. Whether short/meal breaks count depends on duration and whether you're free to leave.

Why it matters

Start with the most common and cheapest causes to narrow it down fast.

Short breaks are often paid in the US.

Step by step

  1. Confirm company/local rules for hours, breaks and overtime.
  2. Record start/end and break minutes daily; don't reconstruct the week later.
  3. Total by week and check duplicates/missing/overnight shifts.
  4. Confirm the overtime threshold (e.g. 40 h/week) before calculating.
  5. Export CSV/screenshot before submitting and keep approval records.

Common mistakes

  • Forgetting breaks, inflating hours.
  • Counting an overnight shift only on the start day and losing hours.
  • Treating 8 h/day as the overtime threshold.
  • Submitting without a copy, leaving no evidence in a pay dispute.

Checklist

  • Daily records, not weekend reconstruction.
  • Breaks/overnight/night shifts handled correctly.
  • Weekly total and OT threshold confirmed.
  • Rate/multiplier/rounding rules confirmed.
  • CSV exported/approval records kept.

Key facts

  • Short breaks are often paid in the US.
  • Bona fide meal breaks may be unpaid.

FAQ

How do I troubleshoot a failed Breaks task?

When Breaks fails, troubleshoot in order: file/format, permission/lock, output settings, another tool. Whether short/meal breaks count depends on duration and whether you're free to leave.

How long does it take?

Usually 1-3 minutes; for intermittent issues, run 30 seconds and retest elsewhere.

Is data uploaded?

Runs locally and does not upload video/audio; extensions may still read the page.

Source: DOL breaks