We have a job with an email trigger that uses an EWS Exchange connection to download the attachments from emails that match the conditions. It has been functioning great, but we noted that the traffic between the exchange server and the VisualCron server is relatively high. The mailbox is 2 GB in size. We have set the trigger conditions to only consider mail received within the last 10 minutes, as well as checking "Keep connection", in an attempt to reduce traffic. Can you advise of any other approaches to reduce the traffic? Currently we are seeing a level of 75 GB per day. I have attached screenshots of the full settings.

We have a job with an email trigger that uses an EWS Exchange connection to download the attachments from emails that match the conditions. It has been functioning great, but we noted that the traffic between the exchange server and the VisualCron server is relatively high. The mailbox is 2 GB in size. We have set the trigger conditions to only consider mail received within the last 10 minutes, as well as checking "Keep connection", in an attempt to reduce traffic. Can you advise of any other approaches to reduce the traffic? Currently we are seeing a level of 75 GB per day. I have attached screenshots of the full settings.

Hi Rob,

I'm not sure there's any other way to reduce the traffic currently. I assume there's a ton of emails being triggered?

---

Hi Michael,

No, currently 2-4 emails a day are being downloaded with attachments ~250KB in size. The mailbox receives approximately 40 emails a day, typically between 3 - 4 pm but we see a constant level of traffic throughout the day (see screenshot). With 95 GB a day we are wondering if it is repeatedly parsing the full mailbox (2GB in size). Otherwise we are not sure why the level of traffic would be so high.

My guess: It checks all emails every time. If you ask it to only consider emails received last 10 mins, it will have to check all emails to see if if they meet that condition or not, and then do the work on the newest emails. It's basically like a full table scan to filter out unwanted records. This can be avoided if one could somehow index this timestamp column, but I guess that's not possible. Howevere there is an easy fix I think: Just move the mails once they have been processed. They arrive in the Inbox, then they are processed by VC, and finally you move the email to another folder that is not monitored by VC. Then you can even remove the 10 minute condition because it will no longer be relevant.

My guess: It checks all emails every time. If you ask it to only consider emails received last 10 mins, it will have to check all emails to see if if they meet that condition or not, and then do the work on the newest emails. It's basically like a full table scan to filter out unwanted records. This can be avoided if one could somehow index this timestamp column, but I guess that's not possible. Howevere there is an easy fix I think: Just move the mails once they have been processed. They arrive in the Inbox, then they are processed by VC, and finally you move the email to another folder that is not monitored by VC. Then you can even remove the 10 minute condition because it will no longer be relevant.

Thomas is correct, this is how it works and the suggested fix is also something I suggest (to move the mails once processed)

---

Thank you both, we have implemented this solution and it appears to be working effectively and as expected. Many thanks again!

Thank you both, we have implemented this solution and it appears to be working effectively and as expected. Many thanks again!

Great! Thanks for confirming

---