Recent AutoTask Errors

Help & Questions
1

We’re getting 2 kinds of errors.

The first is: looks like we got no XML document got the first few 3 days ago, then another 2 days ago, and then dozens last night.
Example:https://console.mspintegrations.com/email2at/advanced/history/1765423093222002vmrv

The second, which only started last night and also had dozens (immediately following the no XML errors) is simply ‘Not Found’
Example:https://console.mspintegrations.com/email2at/advanced/history/1765424833943002zxiz

This happened between 1014 and 1024pm last night… strangely, the API history in AT doesn’t even show these calls. Earlier steps in the ticket processing were able to query the API and return data, and then failed in later steps, so i would expect to see some calls being logged:

image
image953×104 13.4 KB

That gap didn’t appear on the other nights with the no XML errors and I found the corresponding error on the API history side with the same text.

It seems to sort itself out after a bit, but wondering what might be going on? Thoughts?

2

I got these the last couple of nights as well.

3

@DBachen and @KeithTessler

Thanks for reporting this!

These errors are caused when Autotask is offline, as Autotask has been a number of times for pre-planned maintenance over the past few weeks.

We did recently add logic to MSPintegrations to elegantly handle outages from Autotask, but that is apparently not working in every circumstance. Thanks for providing the examples - we’re going to review the specifics and ensure the system works as intended the next time Autotask is unavailable.

When this is working as designed, you’ll see your MSPintegrations emails pause mid-way through until Autotask is available, and then they’ll pick right up where they left off.

Travis