Hi all,
When I ran a scenario which didn’t have any issues before, it stopped when “Get a file” tried to get a file. This scenario processes all the files found in a Dropbox folder and there are 48 images in this specific folder.
It happened on the 18th image, and the input to Operation 18 is:
The URL itself works well. So, I would like to retry if possible.
I wonder how I can retry Operation 18. Any ideas?
Thank you,
Kaz
Oh no, Makita 
You can run the same scenario, but with a filter in between. So fetch all files from the Dropbox folder, but follow it with a filter on bundle order position > 17. This will check all files and will process all files with order position 18 and higher.
(we assume the order of files in the folder stayed the same)
Cheers,
Henk
Thank you, Henk, for the reply. I appreciate it.
So, you are suggesting to add a filer something like the following:
Right? I will try that.
But, we don’t know when this kind of error occurs. Is there any way to add some kind of error handling to Module 14 “Get a file” (shown in the first screenshot in the original post) so that it retries if it stalls with one of the files?
Thank you again.
Kaz
Nope, that is not what I meant.
If you use a List/Search module (e.g. list all files in a Dropbox folder), this will result in a set of bundles. Each bundle is processed individually with its own bundle order number.
Between a module that produces bundles and the rest of the router, you can put a filter like this PandaDoc example:
I am not sure how the rest of your scenario is set up and what your suggestion will result in.
To make the scenario future-proof, you can indeed add an error handling route to try the execution again: https://www.make.com/en/help/errors/error-handlers/directives-for-error-handling
Cheers,
Henk
Thank you very much, Henk. I will learn about the error handling in Make to avoid issues in the future. Thank you for your help and have a great weekend.
Hi Henk, just an update. I was not sure if it was a right way, but I added Break modules when I access to external services (Dropbox and OpenAI in this particular case) as shown below:
and I ran the scenario. I had the following:
I mean the scenario stalled at the OpenAI module at the 84th file. I waited for more than 3 minutes (1 minute interval for 3 times). But, it didn’t output errors and I saw the same screen for a long time.
I thought it didn’t work as expected. But, I figured out that I saw the results in the target app. I opened the scenario with another tab on Chrome and checked the history and it says:
So, in other words, just the scenario’s screen froze for some reason, but everything went fine… Just wanted to let you know what happened.
Hi @Kaz_Suzuki
I’m not sure why did you need to do all this stuff. From beginning of your problem, you could have copy the url from the history and could paste in your HTTP request and run the scenario. That’s it.
For future proof, Break will work.
The steps you have taken has burned unnecessary 100’s of operations. 
Regards,
Msquare Automation - Gold Partner of Make
@Msquare_Automation
@Msquare_Automation, thank you for the message. Your message was beyond my understanding, though. Are you saying that I could copy the URL from the history and run the scenario when I had this issue originally?
I have never tried or even had an idea of copying URL from the history and do something to do with it.
Thank you.
