8.2.4 Mail trigger firing issues - VisualCron - Forum

Community forum

Luke Saunders
2017-02-20T16:30:58Z
I have a job set up with a few email event triggers to download attachments to a local folder and then move the email to a done folder on the server.   month-end-triggers.zip (4kb) downloaded 44 time(s).

They use IMAP/SSL connections to Office365. The connection works as I can navigate the inbox folders within the VisualCron client. The triggers are active, however, the fire count in the trigger editor always shows 0 and it is not doing anything with the emails I've staged to test.


Right now I have 3 of the 4 triggers de-activated but the log appears to show all of them are firing in some way.
2/20/2017 11:20:33 AM Debug ReceiveMail->hashcode: 43853259 (False), Job: Poll acsbad inbox for Comp Exp Budget, Trigger: CompExpBudget Check
2/20/2017 11:20:33 AM Debug ReceiveMail->hashcode: 49529112 (False), Job: Poll acsbad inbox for Comp Exp Budget, Trigger: CompRevBudget Check
2/20/2017 11:20:33 AM Debug ReceiveMail->hashcode: 45839459 (False), Job: Poll acsbad inbox for Comp Exp Budget, Trigger: CompExpForecast Check
2/20/2017 11:20:33 AM Debug ReceiveMail->hashcode: 25678981 (False), Job: Poll acsbad inbox for Comp Exp Budget, Trigger: CompRevForecast Check
2/20/2017 11:20:34 AM Debug ReceiveMail->hashcode: 58310239 (True), Job: Poll acsbad inbox for Comp Exp Budget, Trigger: CompRevBudget Check


thomas
2017-02-21T08:02:03Z
I've had cases where email triggers have fired when inactive. My guess is the they are loaded into memory somehow, and so inactivating a trigger does not have an immediate effect. I had an issue where I had to restart the service to make the trigger stop fireing.
Support
2017-02-21T09:41:14Z
That sounds strange. Did you deactivate the Triggers or the Job prior to this? Were they deactivated manually?
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
Luke Saunders
2017-02-21T14:56:27Z
I have tried just about everything with activating the job and the trigger and running the job manually etc. I've had this issue for quite a while and finally getting around to finding a solution. I just rebuilt the jobs on a clean install to see if it made a difference but its the same thing. At one point on the old system I rebuilt the jobs and when it didnt pull any emails I gave up and did it manually. ( Like 140 single emails and their attachments ) and then the next month when the job came back around and all the triggers were turned off it actually fired when I didnt want it to.. so I deleted the jobs completely and they STILL fired until I restarted the service. So there some kind of bug with loading those email event triggers into and out of run scheduling.
Luke Saunders
2017-02-22T16:32:53Z
We are past this months run and I had a lackey pull all emails for me, but what can I do to help troubleshoot here? I'm happy to send over credentials so you can test the job against our Office365
Scroll to Top