I have a timer that should run every night at midnight, do some processing and send a report email based on the results of a query. (I do have a custom SMTP server configured)
When that codeless timer runs, there is a for loop that should iterate over my result set, and send an email for each object found, accordingly. The problem seems to be that 9 times out of 10, only one of those emails gets sent, say if there are N in the result-set. (I also have print outs throughout, which shows that all of the correct logic is hit, up until the “send email” codeless block, which is as far as I can go). I’m wondering if something is stopping it from sending, since it is so close together via seconds / milliseconds in the loop, that it is being blocked by one of the servers?
Is there any way to check outgoing email logs against my SMTP server from backendless’ side? I’m trying to gain as much context to try and figure out a pattern as to why this is happening / exactly how I can replicate it. I’ve also been in talks with my host to see if they can deduce if the issue is on their end via any logs on their end.
App ID is A324EB2B-1BF5-EB0A-FF36-62F47D198E00.