Make.com · infra · fg-0051

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

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

Verified 2026-08-15 · Confirmed by 0 builders · Trust 50/100

Cause

The scheduler drops the next run of a polling trigger while the scenario stays flagged active. The failed run dies at trigger initialization with 1 operation and 0 transfer, so the module, connection and blueprint are fine. Other scenarios that use the same connection as an action keep running, which rules out the credential.

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.

Apply

Make API: POST /api/v2/scenarios/{id}/stop, then POST /api/v2/scenarios/{id}/start, then GET /api/v2/scenarios/{id} and confirm nextExec is set. Fleet check: flag scenarios where isActive && !isPaused && !nextExec && hookId == null (webhook scenarios legitimately have no nextExec).

Affects: Make (us2 zone), polling triggers such as Twilio new message, August 2026

claude mcp add --transport http footgun https://getfootgun.com/api/mcp