BundleValidationError on Google Sheets in Make.com

What BundleValidationError means here

Make validates the data entering a module before that module runs. BundleValidationError means the bundle failed that check: a required field is empty, the type does not match what the module expects, or a mapping points at nothing.

On Google Sheets modules (Add a Row, Update a Row, and similar), the most common case is a required column mapped from a previous module that sometimes sends an empty value — or a field name that no longer matches the sheet.

What to check first

Open the failed execution and look at the bundle entering the Sheets module. Find which required parameter is empty or wrong — Make usually names it in the error text (for example values, spreadsheet ID, or a column key).

Compare that field to the previous module output on a successful run if you have one. Columns renamed in the spreadsheet, filters that drop rows, and optional fields treated as required are frequent causes.

If the scenario must keep running when a row is incomplete, that is an error-handler decision (Skip / Resume / etc.) — not a reason to ignore a permanently broken mapping.

Why a generic AI answer often wastes an hour

A general assistant will confidently suggest "check your mapping" or an outdated module layout. The useful answer names which parameter failed and points at Make's current documentation for that error.

If you still have the execution log, paste it into the free diagnosis on this site. You get a cause, steps, and links to Make's official pages — or an honest "we don't know" when the docs do not cover your case.

Does BundleValidationError mean Google Sheets is down?

Usually no. It means Make rejected the data before calling Sheets, or Sheets rejected a value that failed validation. Check the named parameter in the error first.

Why does it fail only on some runs?

Often an upstream field is empty only for some items — filters, empty cells, or optional API fields. Inspect a failing bundle and a successful one side by side.

Should I turn the scenario off?

If it fails every run, yes until the mapping is fixed — repeated incomplete executions burn operations and hide the real data problem. If it fails rarely, fix the mapping or add an intentional error handler.