Google Sheet Iteration not working

Status: Open · Asked by Gerhard Visser Jnr on · 0 views

GerhardV — Question ·

Hi - we have an iteration extracting the number of sheets in a google sheet, we do this because each google sheet contains a number of sheets, each sheet with a number of rows in column A (which will be used to create items in monday.com) and then extract the rows in column B to create subitems. So, the problem is that the workflow only creates the first row found in column A, with it's subitems in column B. But it does not go to the remaining sheets.


Resham — Reply ·

Hello,

It appears that you've made some corrections to the workflow—some steps seem to have been deleted. Since this morning, it looks like everything has been functioning correctly.

If you continue to face any issues, please feel free to share a screen recording to help us better understand the problem, and we’ll be happy to assist further.

Resham — Reply ·
Hey,
Thanks for the clarification — we've identified the issue. It seems to be caused by a nested iterator within the router.
Could you please try removing the router and executing the same steps outside of it? That should help isolate and resolve the issue.
Let us know how it goes!
Preeti Paryani — Reply ·

Hello @GerhardV,

Thanks for sharing the details. Please allow us some time to review it.

GerhardV — Reply ·

@Preeti Paryani - any feedback for us?

Preeti Paryani — Reply ·

Hello @GerhardV,

We have escalated this concern to our technical team for review. Please allow us some time and we will get back to you with the updates as we have some.

Preeti Paryani — Reply ·

Hello @GerhardV,

Upon reviewing your workflow, we noticed that in all of the actions, the rows are being retrieved from the same spreadsheet ID; however, the spreadsheet ID has been mapped from a single step across all actions.

We recommend either directly selecting the spreadsheet from the dropdown menu (as it appears to be the same spreadsheet named "Leadership") or entering the spreadsheet ID as a static (raw) value instead of mapping it dynamically.

Once you've made this adjustment, please test the workflow and let us know if it helps resolve the issue.

GerhardV — Reply ·

Hello @Preeti Paryani

I made the changes, and still only get the workflow to run for the first sheet. What we should have seen is multiple main items with subitems, but we only see one main item with its subitems. So the flow works fine, but only for the first sheet.

I also notice the workflow failed with this error:

Preeti Paryani — Reply ·

Hello @GerhardV,

Could you please share the workflow URL along with the Task History ID where you are encountering this issue? This will allow us to better assist you.

Preeti Paryani — Reply ·

Hello @GerhardV,

It appears that some changes in the workflow might not have been saved properly, which could have caused this malfunction. We recommend setting up a new workflow to resolve the issue.

If the problem still persists after setting up the new workflow, we’ll be happy to assist you further over a Google Meet. Kindly try creating the new workflow and let us know how it goes.

Preeti Paryani — Reply ·

Hello @GerhardV,

Upon discussing your use case with our team, we would like to inform you that using a nested iterator (an iterator placed after another iterator) may cause the workflow to malfunction.

However, after reviewing the recently shared workflow, we noticed that you had made changes to a previous workflow, which would not impact the process as expected. We kindly request that you set up a new workflow from scratch by clicking the "Create New Workflow" button and monitor its functioning carefully.

Please let us know if you face any difficulties further. We are here to assist you.

Preeti Paryani — Reply ·

Hello @GerhardV,

Could you please disable the Auto Re-Execution settings for your workflow so we can better investigate the issue.

Preeti Paryani — Reply ·

Hello @GerhardV,

Our team has made some updates on our end, and we kindly request that you test the issue again by creating a new workflow from scratch.

While reviewing your existing workflow, we observed that all actions are retrieving rows from the same spreadsheet. However, the Spreadsheet ID has been dynamically mapped from a single step across all actions.

To ensure smoother execution, we recommend the following:

  • Either select the spreadsheet directly from the dropdown (since it appears to be consistently the same spreadsheet named "Leadership")
    OR
  • Enter the Spreadsheet ID as a static (raw) value instead of mapping it dynamically.

Please give it a try and let us know if you encounter any further issues—we're here to help!

Back to all forum threads · Log in to reply