Scenario editing incorrectly clearing module field values
none- Started
- Jun 30, 5:59 AM EDT
- Resolved
- Jun 30, 4:33 PM EDT
- Duration
- 10h 34m
Make's updates (3)
- monitoring · Jun 30, 5:59 AM EDT
We identified an edge case issue in Datastore Update record module was removing data from fields that were left empty in the module configuration after scenario was edited. Our team already applied the fix and and currently investigating the issue further to confirm the impact. In case you have a suspect your data were affected please contact our support team.
- monitoring · Jun 30, 10:59 AM EDT
Our team identified the root cause and responsible component of the previously reported issue. A bug introduced on June 29, 2026 at 12:17 PM CEST caused null field values to be converted to empty strings when a scenario was edited. Due to the same root cause the blueprints of all scenarios that were edited and saved during the affected period were incorrectly modified. Our team is still analysing the full scope of the impact — the highest confirmed impact is on the Datastore App. The fix was applied on June 30, 2026 at 3:36 PM CEST. All zones are now operating normally. [ACTION REQUIRED] Please perform a hard reload of your browser tab to prevent any further impact. If you edited and saved any scenario between June 29, 12:17 PM CEST and June 30, 3:36 PM CEST, its blueprint may have been incorrectly modified. If you notice unexpected empty fields, please revert to a version saved before June 29, 12:17 PM CEST, or if you need further assistance, please contact our support team to get the data snapshot from before the issue was introduced.
- resolved · Jun 30, 4:33 PM EDT
The incident has been resolved. We have informed the owners of potentially affected organizations by email that they may be affected and what actions to take if they see issues.
What our checks recorded
We checked Make 126 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 982 ms, against 966 ms over the 24 hours before. Make posted the incident at Jun 30, 5:59 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 ↗