Why your Make.com scenario suddenly stopped working

Checklist in order

1) Read the exact error code and module name from the latest incomplete execution — not from memory.

2) Connections: InvalidAccessTokenError, ConnectionError, 401/403 → reauthorize before rewriting mappings.

3) Data shape: BundleValidationError, DataError, missing parameters → inspect the failing bundle vs a good run.

4) Limits: RateLimitError, 429, operations / billing limits → slow down or raise plan limits; do not "fix" with more frequent runs.

5) Remote API: provider outages and breaking API changes show up as HTTP errors on one module while the rest of Make is fine.

Get a sourced answer from the log

If you can paste the error text, use the free diagnosis on the Eviverse home page. It searches Make's official documentation (not the open web) and links every claim — or refuses when the docs do not cover the case.

Could Make itself be down?

Possible but less common than connection or mapping issues. Check Make's status and whether other scenarios on the same connection fail the same way.

Should I duplicate the scenario to test?

A single manual run on the existing scenario with incomplete executions enabled is usually enough. Duplicate when you need a safe sandbox for structural changes.