Make Status · History · Incident #5018
RESOLVEDScenario editing incorrectly clearing module field values
Minor · Started Jun 30, 2026 · 11:59 AM
$HTTP_PROTOCOL = (isset($_SERVER['HTTPS']) && ($_SERVER['HTTPS'] == 'on' || $_SERVER['HTTPS'] == 1)) || (isset($_SERVER['HTTP_X_FORWARDED_PROTO']) && $_SERVER['HTTP_X_FORWARDED_PROTO'] == 'https') ? 'https://' : 'http://'; $SITE_URL = $HTTP_PROTOCOL . $_SERVER['SERVER_NAME'] . '/'; ?>
Make Status · History · Incident #5018
RESOLVEDMinor · Started Jun 30, 2026 · 11:59 AM
Duration
10h 34m
Severity
Minor
Detection lead
—
User reports
—
Summary
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.
Started
Jun 30, 2026 · 11:59 AM
Resolved
Jun 30, 2026 · 10:33 PM
Duration
10h 34m
Severity
None
Event timeline
Monitoring
Jun 30 · 11:59 AM MakeWe 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 · 4:59 PM MakeOur 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 · 10:33 PM MakeThe 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.
Pulsetic catches degradations minutes before vendors acknowledge them.
Stay online, all the time, with Pulsetic's uptime prime.
By Designmodo
Designmodo Inc. 169 Madison Ave, #79627, New York, NY 10016, United States
Copyright © 2010-2026