Make · Help

Make Iterator shows Array: empty despite source data?

The source contains several items but Iterator receives nothing? Check the field path, array type and module reference in the same execution.

Source date: 5 November 2026Editorial team: KAN KAI WORKSEditorially updated:

Quick answer

Array: empty in a Make Iterator describes its received input, not necessarily an absence of source data. An Iterator needs an array; a collection or already separate bundles are different shapes. First open source output and Iterator input from the same execution. Compare field path, type, item count and referenced module ID, especially after scenario changes, before restarting the entire writing workflow.

Source basis: Q1 · Q2

Applies to
The report describes a four-item source array and empty Iterator input after scenario changes. Verify cause and module mapping in the actual run; pagination is a separate issue.
How to verify the result
A neutral two-record array yields two matching outputs; all IDs in the original array then correspond to Iterator outputs before any downstream filtering.
Your first check

What actual value reaches the Array field in this particular execution?

The source module displays an array containing several items, but the following Make Iterator reports Array: empty and processing stops. The useful comparison is at the boundary between those modules: what value reaches the Iterator's Array field in this exact execution?

Available data does not establish correct mapping

An original report describes one source bundle containing four items and an empty Iterator input after scenario changes. It does not establish a universal final cause. Q1 Make documents that an Iterator splits an array into individual bundles. Missing knowledge of the data structure can also affect which fields appear in the mapping panel. Q2

Distinguish a genuinely empty array from an incorrectly referenced property, a collection instead of an array, and a mapping pointing to an earlier module identity.

Inspect the handoff directly

  1. Use the same execution. Open the source output and Iterator input from one run. A successful source test yesterday and a current Iterator test may contain different data.
  2. Record type and path. Is the array at the root, under items, or nested more deeply? Write down the field path and item count. An object with four properties is not automatically an array of four records.
  3. Compare the mapping again. Establish which current module ID the Array field references. Deleting and recreating a module can leave a similar-looking reference pointing elsewhere. Select the relevant array from the current mapping interface instead of typing a module number copied from another scenario.
  4. Expose the structure safely. If fields are absent from mapping, use a harmless example output from the source module. Disconnect downstream writing modules before any learning or test run.
  5. Use a small control. An isolated array containing two neutral records should produce two corresponding Iterator outputs. If it does, focus on the original path and type. If not, preserve Iterator settings and execution context for further investigation.

Verify business completeness

Compare IDs in the input array with all Iterator outputs. Four input items should account for the four expected records before any later filter removes one. Then separately determine whether the source API should supply more pages; missing pagination differs from an empty mapping of an array already present.

Retain the small example and its expected IDs. It gives future scenario edits a clear check without relying on the visual appearance of a mapping token.

Frequently asked questions

Does every search module need an Iterator afterwards?

No. A source that already emits multiple bundles has a different structure. Decide from its actual output.

Is running the entire scenario once sufficient?

Only when its side effects are understood and intended. This diagnosis needs the source structure and Iterator input. An anonymised bundle, field path, module IDs and expected item count are particularly useful for support.

Help with this case

We can help isolate the affected process and prepare a controlled next step. Discuss case A0452 with KAN KAI WORKS.

Support with this issue

We investigate Make using your error message, versions and a narrowly scoped example.

Describe your case →Related service: AI & automation

Sources

Sources checked on 5 November 2026. Individual reports do not establish general prevalence.