Loop only running once, including all data found instead of running multiple times

Hi ​@LARPIT 

Your GSheet step is returning nested arrays, so the nested arrays get flattened.

Post screenshots showing how your GSheet step is configured in these tabs: 

• Setup
• Configure

Nested arrays are probably the immediate cause. The clean test is to make the Google Sheets step return one flat line-item array per column, then map two same-length arrays into Create Loop From Line Items—for example, Row ID and Email—not the Raw Rows object. In the loop preview, iteration 1 should show one scalar Row ID and one scalar Email; if either field still shows the whole bracketed collection, the data is still nested before the loop. Keep Find Spreadsheet Rows outside the loop only if it creates the batch; any per-row lookup belongs inside. The identical email should not collapse iterations by itself, but use Row ID as the loop identity so downstream dedupe does not turn two rows into one.

Hey ​@LARPIT 👋

I did some testing in a Zap and I think it might be nesting the search results like Troy mentioned due to the settings on the Google Sheets action. Not sure which Google Sheets action you’re using but when I tested a Lookup Spreadsheet Row action and set the If multiple search results are found field to Return all results as line items. Step run status is "success" I got a nested set of line items like the one pictured in your screenshot: 

And when I changed the If multiple search results are found field to use the default Return first search result. Step run status is "success". (Default) option instead, it then output multiple rows of data as un-nested line items. For example:

Can you try updating the Google Sheets action in your Zap to use Return first search result. Step run status is "success". (Default) option for the If multiple search results are found field instead? Then, in the Create Loop From Line Items action, you’ll need to reselect the fields from the Google Sheets action and retest it to check it generates the loops correctly.

Next, in the Gmail Send Email actions within the loop select the individual Looping fields and that don’t have the word “Preview” in the name. For example, you’d want to map the Task Name field not the Preview Loop Values Task Name field:

Let us know if that does the trick!