Please note that VisualCron support is not actively monitoring this community forum. Please use our contact page for contacting the VisualCron support directly.


brent.bowen
2016-04-22T19:53:50Z
error2.png error1.png

I have run into an issue where any job that is using an Email Trigger to watch an Office 365 inbox continuously throws a message that the trigger has been inactivated. I have attached two examples of the error message in question. It has become such an issue that we have had to set up an entirely new job to re-enable deactivated triggers every hour. While this is a work-around, I was wondering if there might be something incorrect with my Connection entry, or if VisualCron has trouble with Office 365 inboxes.

Each of the Connections that are a part of the troublesome triggers use the IMAP4 protocol to connect to outlook.office365.com. The connection has no problems when tested, which leaves me a bit unsure what to troubleshoot next.

Any help would be much appreciated.
Sponsor
Forum information
al355
2016-04-22T22:41:51Z
What retry interval have you got set?
brent.bowen
2016-04-23T00:28:09Z
It has a timeout of 180 and retries 30 times. There are 10 triggers exactly like this that monitor various folders within an Office 365 inbox.
Scroll to Top