What is your goal?Improve the scenario’s efficiency or best practices by correctly locating the Tools/Sleep Module.
What is the problem & what have you tried?I am not sure where the best position is for the Tools/Sleep Module to be functionally correct and most efficient. Should I move the Tools/Sleep Module to before the Email Module?
Screenshots (scenario flow, module settings, errors)Hi @Mark68,
It depends on your use case. Could you share why you’re using the Sleep module? Also, is the delay intended for each email or only between batches? That will help determine the best placement.
Best Regards,
@Mohamed_Jahar
Thank you @Mohamed_Jahar for your help.
Sleep mode is being used as a guard against spamming, i.e. delay sending between individual emails.
In your opinion, is 10 seconds a long enough delay between email sending?
Best wishes and regards.
Yeah that’s not going to work. If you are sending bulk emails, you will need to use an external service. Sending them from a Make scenario will get your account flagged no matter what delay you put there.
Thanks @Stoyan_Vatov for your advice. I was hoping to skip that if only a few were sent a day, e.g. 10 or so.
Thanks 
You can put the Sleep module after the Send Email module and use a filter to pause every X sends.
This will save you 9 operations per 10 array items, for example.
Additionally, checking if it isn’t the only/last item, will save you additional operations.
— @samliew
Hello,
If you want to work with ~10 emails per day using 3rd party does not seem necessary but I would strongly encourage to set up a random timer and extend scenario run to even a few minutes.
By this approach your email will look more like human-sent rather than automatic, mass spam.
You can do it, for example, by using:
{{5 + round(random * ((100 - 5) + 1))}}