Iterator processes 3 bundles but downstream modules only run once — Google Drive Download only showing 1 operation

[JaydenW]

What is your goal?

Build an automated content posting pipeline where clients submit photos via Google Form → Make.com downloads the files → uploads to Cloudinary → posts to Instagram via Buffer. For carousel posts I need multiple files to be processed individually through the pipeline.

What is the problem & what have you tried?

My Iterator module shows it processes 3 bundles correctly but every downstream module (Google Drive Download, Cloudinary, Buffer) only runs once — processing only the first file.
Scenario flow:
Webhook → Iterator → Google Drive Download → Cloudinary → Buffer
What I’ve tried:

Deleted and recreated the Google Drive module fresh
Checked for filters on the connection between Iterator and Google Drive — none exist
Confirmed Iterator Array field is correctly mapped
Tried {{11.fileIds}} and separate fields {{11.fileId_1}} etc.
All module connections are active with no filters

Error messages or input/output bundles

Error messages or input/output bundles
Iterator output shows:

Bundle 1 — Value: fileId_1 — Total bundles: 3
Bundle 2 — Value: fileId_2 — Total bundles: 3
Bundle 3 — Value: fileId_3 — Total bundles: 3

Google Drive Download summary: 1 operation — only processes Bundle 1

Screenshots (scenario flow, module settings, errors)

[Marco_Handke]

Your Iterator looks fine: “Operation 1 / Total bundles: 3” is the correct behavior (1 array in → 3 bundles out).

Quick question though: in your Google Drive Download, what is the File ID field actually mapped to? Both {{11.fileIds}} and {{11.fileId_1}} point to the Webhook (module 11), i.e. before the Iterator, don’t they? So the module never sees the 3 bundles and only runs once.

Have you tried mapping it to the Iterator’s output instead (the single file-ID field the Iterator emits)? Curious if that’s been ruled out. That’s usually what causes exactly this “3 bundles but 1 operation” symptom.

[Stoyan_Vatov]

Hey Jayden,

can you show a screenshot from the execution history? Normally they would run only once if the last one produced an error and stopped the rest of the execution. Or you have a filter that stopped the rest from being ran.