Scenarios execution degraded
minor- Started
- Jul 30, 3:55 AM EDT
- Resolved
- Jul 31, 8:35 AM EDT
- Duration
- 28h 40m
Make's updates (4)
- investigating · Jul 30, 3:55 AM EDT
We are currently investigating a minor incident affecting approximately 250 scenarios to fail. Impact appears limited, and our team is actively working to confirm the full scope and root cause. We will provide an update as soon as more information is available.
- investigating · Jul 30, 4:54 AM EDT
Our engineers are continuing to investigate this issue with highest priority. We will provide a further update within the next hour.
- identified · Jul 30, 5:41 AM EDT
We have identified the cause of the scenario execution failures affecting approximately 250 scenarios. Our team is currently re-enabling any scenarios that were disabled as a result, and is working on a fix to prevent this issue from reoccurring. We will provide a further update once the fix has been applied.
- resolved · Jul 31, 8:35 AM EDT
We’re reaching out to let you know that the issue affecting scenario execution has been resolved, and most of the previously disabled scenarios have been re-enabled. Remaining affected scenarios will be handled individually. System execution has stabilized and normal operations have resumed.
What our checks recorded
We checked Make 343 times from Make's start time to its resolution, once every five minutes. Every one of them reached Make's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 998 ms, against 916 ms over the 24 hours before. Make posted the incident at Jul 30, 3:55 AM EDT.
Updates are Make's own words from its status page (status: resolved); we never add an inferred cause. The vendor's incident page ↗