Flow stops depending on order of (datastore) record searches

How To
1

Hi,

I have a scenario where I want to read from two make datastores, one after the other. One datastore (Reminders) is currently empty, the other (Members) has data. I use “search records” with no criteria for both searches to get all records.

If I run the search Members first, the search Reminders executes and the flow continues.

If I run the search Reminders first, the search Members does NOT execute - the flow stops.

I could of course just run search Members first, followed by search Reminders but I’m curious as to why the flow works in one order and not the other.

Happy to hear if anyone can explain what is going on.

Thanks,

Tony

3

Hey Tony,

can you share some screenshots? Usually there is a setting to continue after empty executions. Maybe that wasnt toggled on one of the runs?

4

Hi Stoyan,

Thanks for the response. I checked and yes, the “Continue after empty execution” is NOT checked in either of the datastore search records modules so that is most likely the cause of the problem.

I have modified the scenario significantly since I made the post because I’m learning SO MUCH about the limitations of make with regard to data scope! I had assumed that when you searched for records the array of results would be available for use later in the flow but this appears to not always be true. So I have added a bunch of set variable modules to capture the data date that is read and extracted from http GET so I can be assured of being able access everything I need later in the flow.

Again, thanks for the response.

Regards,

Tony

5

Yeah most Search modules dont return the array it self. Instead they already iterate on it and provide a separate bundle for each entry found. If you want the results in an array, then you need to use an aggregator module after the search module.