Outage in Mode

Legacy Chart Table generates "no rows returned" when data present

Resolved Minor
June 28, 2022 - Started almost 2 years ago - Lasted about 14 hours
Official incident page

Need to monitor Mode outages?
Stay on top of outages with IsDown. Monitor the official status pages of all your vendors, SaaS, and tools, including Mode, and never miss an outage again.
Start Free Trial

Outage Details

Status as of 2022-JUN-28, 11AM EDT, 8AM PDT: The issue has been identified and our Engineers are working on a fix. At roughly 6PM EDT on Monday, June 27th, two clients alerted us of Report Builder behavior where some charts incorrectly rendered, "No rows returned," error when data was present. Our Engineers identified and confirmed the issue and began actively working on it. At roughly 8:30PM EDT Monday, a third client confirmed the issue, and we escalated the behavior to an incident. There are four workarounds available: 1. Users may view the results to view the data. 2. Users may convert their legacy Table charts to Quick Chart: Tables. 3. Users may download the results and view the CSV. 4. Users with edit access may run the SQL Report's underlying queries to validate data exists. We recommend the second solution, but all are viable at this time. Thank you for your patience. Edit: The first incident post indicated the first incidents occurred at roughly 7PM. The incidents were reported to us at at 5:40PM and 6PM respectively. The Status Page has been updated to refine the initial reported time's accuracy.
Components affected
Mode Report Run Scheduler
Latest Updates ( sorted recent to last )
IDENTIFIED almost 2 years ago - at 06/28/2022 01:35AM

Status as of 2022-JUN-28, 11AM EDT, 8AM PDT: The issue has been identified and our Engineers are working on a fix.

At roughly 6PM EDT on Monday, June 27th, two clients alerted us of Report Builder behavior where some charts incorrectly rendered, "No rows returned," error when data was present. Our Engineers identified and confirmed the issue and began actively working on it. At roughly 8:30PM EDT Monday, a third client confirmed the issue, and we escalated the behavior to an incident.

There are four workarounds available:
1. Users may view the results to view the data.
2. Users may convert their legacy Table charts to Quick Chart: Tables.
3. Users may download the results and view the CSV.
4. Users with edit access may run the SQL Report's underlying queries to validate data exists.

We recommend the second solution, but all are viable at this time.

Thank you for your patience.

Edit: The first incident post indicated the first incidents occurred at roughly 7PM. The incidents were reported to us at at 5:40PM and 6PM respectively. The Status Page has been updated to refine the initial reported time's accuracy.

Start monitoring Mode and all your cloud vendors in minutes

With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.

Start free trial

No credit card required · Cancel anytime · 3153 services available

Integrations with Slack Microsoft Teams Google Chat Datadog PagerDuty Zapier Discord Webhook

Setup in 5 minutes or less

How much time you'll save your team, by having the outages information close to them?

14-day free trial · No credit card required · Cancel anytime