Make: BundleValidationError
Last verified
BundleValidationErrorWhat it means
Make raises BundleValidationError when the bundle that enters a module does not pass validation. Unlike DataError, this check happens in Make before anything is sent to the app: a required field is empty, or a mapped value has the wrong type for the field.
The most common trigger is an empty mapping. A search module earlier in the scenario returned no results, or the trigger record lacked a field, so the required input is blank. The error message usually names the missing or invalid parameter.
Without error handling, the run ends with an error and counts toward consecutive errors, which can lead Make to disable scheduling.
What is not wrong: the app and the connection; the request never left Make.
What it looks like
BundleValidationError
Validation failed for 1 parameter(s).
Missing value of required parameter 'email'.
Filter before module: email ExistsWhy it happens
- A required field is mapped from a value that is empty for this bundle.
- An earlier search returned no results, so its outputs are empty.
- A value has the wrong type (text into a number or date field, an array into a single field).
- The trigger data structure changed and mappings point to fields that no longer exist.
How to fix it
- Read the parameter name in the error and open the module's input in scenario history.
- Trace the empty value back to the module that should have produced it.
- Add a filter before the module that only passes bundles with the required values.
- Use ifempty() or a default value for optional data, and type conversion functions for wrong types.
- Re-run the scenario to confirm.
How to stop it recurring
Filter out incomplete bundles early, use defaults for optional fields, and handle the "no results" path from search modules explicitly.
Official documentation: help.make.com/fix-missing-data-errors. See all Make error messages or the Make limits and quotas.
Related errors
Definitions
- Make (formerly Integromat)Make (formerly Integromat) is a visual automation platform that connects apps and designs complex workflows us
- Error HandlingError handling is the practice of anticipating, detecting, and responding to errors in software execution, inc
- Rate LimitingRate limiting is a technique that controls the number of requests a client can make to a server within a given
- Retry LogicRetry logic is a fault-tolerance pattern that automatically re-attempts failed operations with configurable de
Quick answers
What does "BundleValidationError" mean in Make?
Make raises BundleValidationError when the bundle that enters a module does not pass validation. Unlike DataError, this check happens in Make before anything is sent to the app: a required field is empty, or a mapped value has the wrong type for the field. The most common trigger is an empty mapping.
How do I fix "BundleValidationError"?
1. Read the parameter name in the error and open the module's input in scenario history. 2. Trace the empty value back to the module that should have produced it. 3. Add a filter before the module that only passes bundles with the required values. 4. Use ifempty() or a default value for optional data, and type conversion functions for wrong types. 5. Re-run the scenario to confirm.
Error handling you can see in the workflow
Autonoly workflows have per-node retries, timeouts, continue-on-fail and error-handler branches, so a failing step can be retried or routed instead of stopping the whole run. Saved workflows have no loop node; lists are worked through by the AI agent or one run per trigger item.
Also see Visual workflow builder.