Scenario editing incorrectly clearing module field values

What to do

• Check whether you use Make eu1.make.com, eu2.make.com, us1.make.com, us2.make.com and 2 more. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 10h 34m it lasted.

  Anything that failed between 2026-06-30 09:59 UTC and 2026-06-30 20:33 UTC may need a replay.

• Subscribe to Make's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=make works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Make 3

1. monitoringJun 30, 2026, 9:59 AM UTC

   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.

   provider

2. monitoringJun 30, 2026, 2:59 PM UTC

   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.

   provider

3. resolvedJun 30, 2026, 8:33 PM UTC

   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.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.