Help for owners
My Make scenario shows mapping or bundle errors
Short answer
Make can only map what a module has already returned in its bundle, so a mapped field is empty if the earlier module did not run or returned something else. Arrays need an index or an iterator, and outputs between an iterator and aggregator are not available after the aggregator.
Does this sound like your situation?
- A field is empty in the next module even though the data exists.
- I get one record where I expected a list, or the reverse.
- The scenario worked in a test and fails on real data.
- Items after the aggregator are missing.
- I changed a module and later modules broke.
Why does this happen?
You can only map what a bundle holds
Make explains that you can map any information a module gets in a bundle, and that you only see what is available by running the source module and inspecting its bundle. A module that has never run has nothing to map.
Confirmed by help.make.com
Arrays need an index or an iterator
Mapping an array item without an index returns the first element, and the index in square brackets selects another. An Iterator converts the array to a series of bundles.
Confirmed by help.make.com
Outputs vanish after an aggregator
Make states that outputs of modules wrapped between an Iterator and an Aggregator are not accessible beyond the Aggregator.
Confirmed by help.make.com
Different data types
A bundle holds a single value, an array holds one kind of information and a collection can mix kinds. Mapping one into a field that expects another fails or gives empty results.
Confirmed by help.make.com
Real data differs from test data
Optional fields, empty lists or a single item instead of many make a scenario behave differently from the test run.
What can I do about it today?
- Open the failed run and inspect the bundleLook at the input and output of the failing module.
- Find the first module where data differsThe error often starts earlier than where it shows.
- Rerun with one real recordTest with a normal order and an odd one: empty fields, a single item, a long list.
- Do not remap everything at onceChange one module at a time and test after each change.
- Duplicate the scenario before editingExperiment on a copy so the live one keeps running.
When should I bring someone in?
- The scenario writes to invoices, payments or customer records.
- Nested lists, aggregators and several iterators are involved.
- The scenario was built by someone no longer around.
How do I handle it?
- Trace the dataI follow one record through each module, noting its type and shape at each step.
- Handle the odd casesEmpty values, single items and missing fields get explicit handling instead of defaults.
- Simplify the structureChains of iterators and aggregators are reduced where the app offers a batch call.
- Test with real samplesI keep example inputs for normal and odd cases and rerun them after every change.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
Why does a mapping work in a test and fail live?
Test data is usually complete and live data is not. Check empty fields, single items and unusual values.
Why can I not use a module's output after the aggregator?
Make states that outputs from modules between an iterator and aggregator are not accessible beyond the aggregator.
Is it a Make fault?
Usually the data does not match what the mapping expects. The bundle inspection shows it.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.