Mode: Scheduled Report Failures
Timeline of updates
- resolved
We became aware of an issue affecting scheduled reports executions beginning around 11:00 PM EST on November 17th. The issue affected hourly, 15-minute, and weekly scheduled jobs. Monthly and 30-minute schedules were not impacted. Engineering has resolved the issue, and normal scheduling has resumed. We are continuing to monitor to ensure full stability. Further updates will be provided.
Edit: Scheduled executions began failing at 2:00 PM EST on November 17 and were fully resolved by 6:30 AM EST on November 18.
As expected after recovery, some delayed or duplicate scheduled runs were triggered as jobs caught up. Normal scheduling has now resumed as of Nov 20.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-11-04 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
34e3f4341ec69bb9…
Impact, status and times are the vendor’s own, as last archived. View on status.modeanalytics.com (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by Mode, started 2025-11-18 13:00 UTC, resolved after 0 min, 1 update(s).
- Title
- Scheduled Report Failures
- Vendor
- Mode
- Date
- URL
- https://rewindex.com/company/mode/incidents/mn4twc8b7b6h
Mode profileRecent Mode incidentsAll outages on November 18, 2025Mode in November 2025MarkdownJSON