Make.com breaking changes, updated weekly

Every verified Make.com trap in Footgun: changes and behaviors that break code or give wrong results, newest first. Each one has the error you see, the fix, and the date it was last checked. The list updates when the weekly check adds or retires a trap. For the full cause and sources, open the trap, or see all Make.com traps.

1. fg-0056· added 2026-10-13· last checked 2026-10-13

   Variables in one 'Set multiple variables' module cannot reference each other

   Symptom

   A variable built from a sibling variable in the same module comes out empty

   Fix

   Compute each variable from the original source fields, or chain two modules.

2. fg-0036· added 2026-10-08· last checked 2026-10-08

   Data store 'Search records' with no results silently ends the run

   Symptom

   Modules after the search never execute

   Fix

   Turn on continue-when-no-results for any search that can legitimately miss, or follow it with an array aggregator, which emits once even when empty, and branch on the aggregated length. Comparing operations per run between good and bad runs shows where a flow stopped.

3. fg-0038· added 2026-10-08· last checked 2026-10-08

   Data store 'Update a record' blanks every field you did not map

   Symptom

   Fields that held values before an update are empty afterwards

   Fix

   Map every field on every update, carrying unchanged values from an earlier Get or Search.

4. fg-0044· added 2026-10-08· last checked 2026-10-08

   Google Calendar 'Make an API call' returns 404 when the calendar id is URL-encoded

   Symptom

   404 Not Found for /v3/calendars/name%40example.com/events/{id}

   Fix

   Write the calendar id with a raw @ in the path. Debug errors like this in a throwaway scenario with no error handler, because an Ignore handler hides the message.

5. fg-0037· added 2026-10-08· last checked 2026-10-08

   Data store search results map as empty because fields sit under .data

   Symptom

   {{3.status}} is always empty

   Fix

   Map {{N.data.field}}. Store a text status or a date where you need to search, not a boolean.

6. fg-0039· added 2026-09-30· last checked 2026-09-30

   Formula with an escaped quote passes validation but fails at run time

   Symptom

   BlueprintValidationError: Scenario validation failed - 2 problem(s)

   Fix

   Keep quote characters out of formula strings. To match text that contains quotes, use a regex with \W or . where the quote would be.

7. fg-0052· added 2026-09-18· last checked 2026-09-18

   Running a webhook-triggered scenario through the API succeeds with 0 operations

   Symptom

   Run returns success with 0 operations

   Fix

   Trigger webhook scenarios by sending an HTTP request to the webhook URL. To run modules on demand from the API, build an action-only scenario with no trigger and on-demand scheduling; a run then executes each module once in module id order.

8. fg-0033· added 2026-09-14· last checked 2026-09-14

   Blueprint update fails with 'should NOT have additional properties'

   Symptom

   400 should NOT have additional properties

   Fix

   Strip scheduling and interface from the blueprint before sending it, and pass scheduling as its own field if you need to change it.

9. fg-0055· added 2026-09-04· last checked 2026-09-04

   'Trigger cannot be handled when processing an incomplete execution' warning on polling scenarios

   Symptom

   Email subject: Encountered warnings in scenario

   Fix

   Take no action when the scenario has no incomplete executions, is not waiting, is active and has nextExec set. Do not deactivate and reactivate: on a polling trigger that can reset its position and skip real items. Act only if the warning turns daily or incomplete executions start to pile up.

10. fg-0048· added 2026-09-02· last checked 2026-09-02

    One bad item makes a polling trigger retry the same item forever and block everything behind it

    Symptom

    The same error repeats every polling interval

    Fix

    Add a filter right after the trigger that requires every field later modules treat as required, so malformed items are skipped and the position advances. Remove unused modules that declare required inputs.

11. fg-0053· added 2026-09-02· last checked 2026-09-02

    Scenario is switched off after you save it in the editor or update its blueprint

    Symptom

    Scenario is not activated

    Fix

    After every edit, start the scenario again and confirm it is active and that a clean run follows.

12. fg-0031· added 2026-08-15· last checked 2026-08-15

    429 'Requests limit for organization exceeded' when scanning many scenarios

    Symptom

    429 Requests limit for organization exceeded

    Fix

    Retry 429 and 5xx with exponential backoff that honors Retry-After, and pause a few hundred milliseconds between scenarios. Report a throttled read as unchecked, not as a failing scenario.

13. fg-0051· added 2026-08-15· last checked 2026-08-15

    Polling scenario stops with 'Invalid type of a module' and never runs again

    Symptom

    InvalidConfigurationError: Invalid type of a module when processing data, where the type is: 'undefined'

    Fix

    Deactivate the scenario, then activate it again. Activating alone changes nothing because Make believes it is already on. The fix has landed when nextExec is populated again. On restart the trigger resumes from its stored position, so items that arrived during the stall are picked up.

14. fg-0050· added 2026-08-15· last checked 2026-08-15

    Polling scenario shows no executions for hours but is still running

    Symptom

    History shows no runs for hours on a scenario that polls every 15 minutes

    Fix

    Judge liveness from nextExec, not from gaps in history. A healthy poller has nextExec in the future and it moves forward one interval after each poll.

15. fg-0043· added 2026-08-10· last checked 2026-08-10

    Gmail watch scenario that emails an alert to its own mailbox loops forever

    Symptom

    The same alert email arrives every polling interval

    Fix

    Add a filter right after the trigger that drops your alert prefix, and never copy the incoming subject into an alert subject (put it in the body). Better still, use a Gmail search with a processed label excluded in the query and add the label as the last step. That makes reprocessing idempotent and lets a missed message be picked up again.

16. fg-0034· added 2026-08-04· last checked 2026-08-04· stale, may be out of date

    'Cannot initialize the scenario' with 0 operations looks like a dead connection but self-heals

    Symptom

    Cannot initialize the scenario because of the reason

    Fix

    Check whether the next run of the same scenario succeeded. If it did, do nothing and do not reconnect healthy connections. In monitoring, suppress an isolated failure with this signature when a later run succeeded, and alert only when it repeats on consecutive runs.

17. fg-0049· added 2026-07-18· last checked 2026-07-18· stale, may be out of date

    Opening a CRM module in the Make editor shows a mapped lookup empty, and saving wipes it

    Symptom

    Contact ID renders empty with its Map toggle off

    Fix

    Do not edit these modules in the editor. Fetch the blueprint, change the mapper in code, and write it back through the API.

18. fg-0032· added 2026-07-18· last checked 2026-07-18

    Bigin module fails with 'Provided account is not compatible'

    Symptom

    Provided account is not compatible

    Fix

    Use the version 2 module names and set version 2 on each module. Copy module ids from a working scenario's blueprint.

19. fg-0040· added 2026-07-17· last checked 2026-07-17

    Gmail 'Make an API call' module returns 404 for /gmail/v1 paths

    Symptom

    404 on a path that works in the Gmail API reference

    Fix

    Start the path at /v1.

20. fg-0035· added 2026-07-16· last checked 2026-07-16

    Creating a custom webhook through the API returns 400 for missing parameters

    Symptom

    400 on POST /hooks with typeName gateway-webhook

    Fix

    Send all three explicitly.

21. fg-0054· added 2026-07-11· last checked 2026-07-11

    Scenario logs endpoint rejects pg[limit] above 50 and ignores the status filter

    Symptom

    400 SC400 Available maximum limit 50

    Fix

    Page in steps of 50 with pg[offset] and filter for status 3 in your own code.

22. fg-0046· added 2026-07-11· last checked 2026-07-11

    Incomplete executions endpoint returns 'Missing required parameter scenarioId'

    Symptom

    400 Missing required parameter scenarioId

    Fix

    List active scenarios first, then query each one. A replay resumes from the failed step. The API token needs the dlqs:read and dlqs:write scopes.

23. fg-0041· added 2026-07-08· last checked 2026-07-08

    Gmail search module returns emails with empty bodies

    Symptom

    Body is empty in every bundle

    Fix

    Set format to full, turn on the HTML body option, and map fullTextBody or htmlBody.

24. fg-0047· added 2026-06-24· last checked 2026-06-24· stale, may be out of date

    New Gmail watch scenario processes hundreds of old emails on first activation

    Symptom

    The first runs after activation act on historical emails

    Fix

    Before turning the scenario on, set the trigger's starting point to From now on.