Hi Make Community, I’m encountering a perplexing issue where my workflows are repeating unexpectedly, even when I specifically select “Run once”. This repetition consistently seems to begin after the “Get Current Date” module in my scenarios, despite expecting a single execution per “Run once” trigger.
This is happening across multiple automations, including a simple workflow with only a few modules (Watch Google Sheet Rows, GPT, and Google Docs integration). My primary workflow involves processing email attachments, using GPT for data extraction and structuring, and then updating Google Sheets. I suspect the Repeater modules or possibly the Google Sheets modules (“Match Product Names”) might be involved, but I’m unsure why the repetition occurs even in “Run once” mode, especially after the date module.
Has anyone else experienced similar workflow repetition in “Run once” mode, or have any insights into potential causes or troubleshooting steps? I’d be happy to provide more details or workflow configurations and run logs if needed to help diagnose this issue. Any assistance would be greatly appreciated!
Welcome to the Make community!
You were not aggregating the multiple results from the “Search Rows” module. If you are expecting a single result, then you have to set the bundle limit to 1.
Combining Bundles Using Aggregators
Every result (item/record) from trigger/iterator/list/search/match modules will output a bundle. This can result in multiple bundles, which then trigger multiple operations in future modules (one operation per bundle). To “combine” multiple bundles into a single variable, you’ll need to use an aggregator of some sort.
Aggregators are modules that accumulate multiple bundles into one single bundle. An example of a commonly-used aggregator module is the Array aggregator module. The next popular aggregator is the Text Aggregator which is very flexible and can apply to many use-cases like building of JSON, CSV, HTML.
You can find out more about the other types of aggregator modules here:
Mapping a Specific Structure Into a Complex Field
The Array Aggregator module is very powerful because it allows you to build a complex array of collections for a later module’s field to map multiple items (collections) to it.
This is done using the “Target structure type” field in an Array Aggregator module.
Here is an example:
As you can see, the “Map” toggle on complex fields are used when you have an array. You can easily build an array variable to map to a future module’s field, by using an Array Aggregator module and select the “Target Structure Type” as the future module’s field you have mapped the array into.
Here are some useful links and guides you can use to learn more on how to use the Make platform, apps, and app modules. I found these useful when I was learning Make, and hope they might benefit you too —
Getting Started
Help Centre Basics
Articles & Videos
Hope this helps! Let me know if there are any further questions or issues.
— @samliew
P.S.: Investing some effort into the Make Academy will save you lots of time and frustration using Make.
