Automation Answers

Why Is My Make Scenario Failing With DataError?

A Make DataError means a module got data it could not accept: a wrong type, a bad date or number format, a missing required value, or a value the app rejects.

By Automation Ace Editorial Team · Reviewed for technical accuracy by Troy Tessalone · Published · Updated

Short answer

Why Is My Make Scenario Failing With DataError?

A DataError in Make means the data passed to a module, or sent on to the app, wasn't valid. Usually a mapped field has the wrong type, a date or number is in a format the module can't read, a required value is empty, or the app rejected the value. Open the failed bundle in the run history, compare the mapped values with what the module expects, and convert or validate them before that step.

Common causes

  • A date is in a format the module can't parse, such as 10/27/26 instead of an ISO date.
  • A number contains commas or a currency symbol, or text is mapped into a number field.
  • A required field is blank in this run.
  • An array or collection is mapped where a single value is expected, or the reverse.
  • The app rejected a value, such as an invalid option, email, or ID.

Diagnostic steps

  1. Open the run history and click the failed module to see the input bundle and the error message.
  2. Compare each mapped value with the field type the module expects.
  3. Convert values with functions such as parseDate(), formatDate(), parseNumber(), and toString().
  4. Add a filter or ifempty() default so blank required fields don't reach the module.
  5. Add an error handler that logs the bad bundle and alerts someone, rather than stopping the whole scenario.

Example

A scenario creates CRM deals from a form. Some runs fail with a DataError because the amount arrives as $2,500. Mapping parseNumber(replace(amount; "$"; emptystring); ".") sends 2500 instead, and the runs succeed.

Caveats

Retrying a DataError usually fails again until the data or mapping is fixed. Use a Resume or Ignore handler only when skipping or defaulting the value is genuinely safe.