How to find cause of mailbox export failure

0

I set up a Cloudwatch rule to schedule a Lambda to call Boto3's start_mailbox_export_job on a Workmail mailbox. The Lambda checks the JobId to ensure it didn't immediately fail, logs the job information, and quits. However, I noticed later when I used describe-mailbox-export-job through the CLI that the export job failed after some 5 hours and 30 minutes. The API doesn't offer any insight into the cause of the failure. Is there any way to obtain this information?

asked 3 years ago246 views
6 Answers
0

Hi,

I'm sorry to hear you're experiencing problems with the mailbox export of your user. I checked with the service team and the confirmed there was a problem that has been fixed. You should be able to try again.

The team also mentioned that the error output needs to be improved and will work on that.

Kind regards,
Robin

AWS
EXPERT
answered 3 years ago
0

Hello, Robink,

Unfortunately, another automated export ran today, but failed after 5.5 hours. Is there no way to gain any insight on what's happening?

I manually triggered the lambda yesterday on a smaller test mailbox, which completed without issue, so I know it's not a mundane problem like inadequate permissions.

Edited by: brianbauman on Feb 9, 2021 7:54 PM

answered 3 years ago
0

Hi,

I'm very sorry to hear that. I will contact the service team to investigate this.

Kind regards,
Robin

AWS
EXPERT
answered 3 years ago
0

I appreciate your efforts, Robin.

If it's helpful, both exports started around 17:15 UTC and failed a bit over 5 hours later at around 22:30 UTC.

So perhaps the mailbox exporter times out after 5-ish hours? Or possibly there's some sort of regular maintenance or scheduled event at ~22:30 UTC that interrupts any mailbox exports running at that time?

Just some thoughts.

~Brian

answered 3 years ago
0

Hi Brian,

The service team checked your error and pushed out another fix. Could you try to do the export again?

Kind regards,
Robin

AWS
EXPERT
answered 3 years ago
0

That last change seems to have shaken something loose - today's scheduled backup completed successfully after only an hour and 14 minutes. Hopefully that remains consistent. Thanks for looking into it!

answered 3 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions