Office-js: Office.context.mailbox.item.body.getAsync returns error 9020 An internal error has occured
Since a few days we get an error response 9020 on the call Office.context.mailbox.item.body.getAsync. This code used to work flawless. Is there a Microsoft problem?
Current Behavior
value: null
status: failed
error: OSF.DDA.Error
name: GenericResponseError
message: An internal error has occurred.
code: 9020
Steps to Reproduce, or Live Example
function getEmailBody() {
Office.context.mailbox.item.body.getAsync(Office.CoercionType.Text, function callback(asyncResult) {
return asyncResult.value;
});
We have launched addin using OWA chrome browser.
anilreddyr7
All 23 comments
I have the same issue!
wuarmin
on 9 Jan 2020
@exextoc Do you have any idea on this? Is it known issue?
anilreddyr7
on 9 Jan 2020
We experience the same issue.
plamenbotev
on 9 Jan 2020
@exextoc Hi, it looks like several customers are experiencing the same issue. thanks for investigating, lindalu
lindalu-MSFT
on 10 Jan 2020
@exextoc @macOutlookExtensibility Please note that there are also two Stack Overflow unanswered questions about this same issue:
lindalu-MSFT
on 10 Jan 2020
@anilreddyr7 / @wuarmin / @plamenbotev
- Can you check whether there are any other console errors and share it with us?
- Is the API with CoercionType.Text always failing or is it failing with complex HTML content in the body?
- Can you share your add-in with us?
This will help us reproduce the issue on our end.
exextoc
on 10 Jan 2020
@exextoc In our use case, we are loading a mail from the addin in new popup.
After that, we are using the addin in the newly opened popup.
This use case was working properly for us for some time.
- in any addin, open any message using
window.Office.context.mailbox.displayMessageForm - in the newly opened message open the addin again
- execute
Office.context.mailbox.item.body.getAsync('text', {} , function (result) { console.log(result); }); - We get the reported error instead the body of the loaded mail.
We are able to reproduce the issue using the latest chrome version and IE 11.
plamenbotev
on 10 Jan 2020
Thanks for reporting this issue regarding body.getAsync() in pop out window. It has been put on our backlog. We unfortunately have no timelines to share at this point
exextoc
on 12 Jan 2020
I am also having issues with Office.context.mailbox.item.body.getAsync returning error 9020.
Mac Outlook desktop client is fine both standard inline view and popout.
Mac Chrome in composing context is fine both standard inline view and popout.
Mac Chrome in reading context inline view returns the error often but on occasion passes.
Mac Chrome in reading context with the email in a new window returns the error.
Mac Firefox and Safari also return the error when in a popout email in reading context.
No windows tests run.
Can you check whether there are any other console errors and share it with us?
No console errors
Is the API with CoercionType.Text always failing or is it failing with complex HTML content in the body?
Simple text or large html have the same results
cbishop-fv
on 13 Jan 2020
I am also having issues with Office.context.mailbox.item.body.getAsync returning error 9020.
Mac Outlook desktop client is fine both standard inline view and popout.
Mac Chrome in composing context is fine both standard inline view and popout.
Mac Chrome in reading context inline view returns the error often but on occasion passes.
Mac Chrome in reading context with the email in a new window returns the error.
Mac Firefox and Safari also return the error when in a popout email in reading context.
No windows tests run.Can you check whether there are any other console errors and share it with us?
No console errors
Is the API with CoercionType.Text always failing or is it failing with complex HTML content in the body?
Simple text or large html have the same results
Do you have any test account to reproduce this issue?
exextoc
on 14 Jan 2020
value: null
status: failed
error: OSF.DDA.Error
name: GenericResponseError
message: An internal error has occurred.
code: 9020
It is not working for my running app which been working from a long while. suddenly stopped and throwing an error I mentioned above.
Anishmourya
on 14 Jan 2020
I replicated above issue on "Office 365 E3" based accounts, while its working fine on "Office 365 Business Essentials" based accounts.
Anishmourya
on 14 Jan 2020
I am also having issues with Office.context.mailbox.item.body.getAsync returning error 9020.
Mac Outlook desktop client is fine both standard inline view and popout.
Mac Chrome in composing context is fine both standard inline view and popout.
Mac Chrome in reading context inline view returns the error often but on occasion passes.
Mac Chrome in reading context with the email in a new window returns the error.
Mac Firefox and Safari also return the error when in a popout email in reading context.
No windows tests run.Can you check whether there are any other console errors and share it with us?
No console errors
Is the API with CoercionType.Text always failing or is it failing with complex HTML content in the body?
Simple text or large html have the same results
Do you have any test account to reproduce this issue?
I am using a free outlook account to test.
cbishop-fv
on 14 Jan 2020
We experience the same issue across environments.
We call Office.context.mailbox.item.body.getAsync only in one place in the code.
The error code can be different:
9020 GenericResponseError- chrome, firefox, opera5001 Internal Error- edge, ie9030 APICallFailedDueToItemChange- apple mail
We've tried to do retries every 1 second. And it seems to fix it in 13% of cases for the first attempt, and in 5% of cases for the second attempt.
Here is some collected data for issue occurrence. Hope this will help.
|ID |User |Browser |Browser.Name|Device|Device.Family|Environment|Getemailbody.Code|Getemailbody.Message |Getemailbody.Name |Level |Msg |OS |Os.Name |Outlook.Accounttype|Outlook.Host|Outlook.Hostname|Outlook.Hostversion|Outlook.Owaview|Outlook.Platform|Outlook.Version |
|----------------------------------------------|--------|-------------------|------------|------|-------------|-----------|-----------------|---------------------------------------|----------------------------|-------|------------------|----------------|----------|-------------------|------------|----------------|-------------------|---------------|----------------|----------------|
|Jan 16, 2020 8:49:48 AM UTCgetEmailBody.error |
|Jan 16, 2020 8:49:47 AM UTCgetEmailBody.error |
|Jan 16, 2020 8:49:46 AM UTCgetEmailBody.error |
|Jan 16, 2020 8:16:11 AM UTCgetEmailBody.error |
|Jan 16, 2020 8:16:10 AM UTCgetEmailBody.error |
|Jan 16, 2020 8:16:09 AM UTCgetEmailBody.error |
|Jan 16, 2020 8:16:09 AM UTCgetEmailBody.error |
|Jan 16, 2020 8:16:08 AM UTCgetEmailBody.error |
|Jan 16, 2020 8:16:07 AM UTCgetEmailBody.error |
|Jan 16, 2020 8:16:06 AM UTCgetEmailBody.error |
|Jan 16, 2020 8:16:06 AM UTCgetEmailBody.error |
|Jan 16, 2020 8:16:06 AM UTCgetEmailBody.error |
|Jan 16, 2020 8:16:05 AM UTCgetEmailBody.error |
|Jan 16, 2020 8:16:04 AM UTCgetEmailBody.error |
|Jan 16, 2020 8:16:04 AM UTCgetEmailBody.error |
|Jan 16, 2020 8:16:01 AM UTCgetEmailBody.error |
|Jan 16, 2020 8:16:00 AM UTCgetEmailBody.error |
|Jan 16, 2020 8:15:59 AM UTCgetEmailBody.error |
|Jan 16, 2020 8:15:59 AM UTCgetEmailBody.error |
|Jan 16, 2020 8:15:47 AM UTCgetEmailBody.error |
|Jan 16, 2020 8:15:46 AM UTCgetEmailBody.error |
|Jan 16, 2020 8:15:45 AM UTCgetEmailBody.error |
|Jan 16, 2020 8:15:45 AM UTCgetEmailBody.error |
|Jan 16, 2020 7:45:37 AM UTCgetEmailBody.error |
|Jan 16, 2020 7:45:36 AM UTCgetEmailBody.error |
|Jan 16, 2020 7:45:35 AM UTCgetEmailBody.error |
|Jan 16, 2020 7:45:32 AM UTCgetEmailBody.error |
|Jan 16, 2020 7:45:30 AM UTCgetEmailBody.error |
|Jan 16, 2020 7:31:15 AM UTCgetEmailBody.error |
|Jan 16, 2020 7:31:14 AM UTCgetEmailBody.error |
|Jan 16, 2020 7:31:13 AM UTCgetEmailBody.error |
|Jan 16, 2020 6:10:42 AM UTCgetEmailBody.error |
|Jan 16, 2020 6:10:41 AM UTCgetEmailBody.error |
|Jan 16, 2020 6:10:40 AM UTCgetEmailBody.error |
|Jan 16, 2020 4:22:27 AM UTCgetEmailBody.error |
|Jan 16, 2020 4:22:26 AM UTCgetEmailBody.error |
|Jan 15, 2020 11:11:55 PM UTCgetEmailBody.error|
|Jan 15, 2020 8:07:47 PM UTCgetEmailBody.error |
|Jan 15, 2020 8:07:47 PM UTCgetEmailBody.error |
|Jan 15, 2020 6:55:48 PM UTCgetEmailBody.error |
|Jan 15, 2020 6:55:47 PM UTCgetEmailBody.error |
|Jan 15, 2020 11:31:41 AM UTCgetEmailBody.error|
|Jan 15, 2020 11:31:41 AM UTCgetEmailBody.error|
|Jan 15, 2020 11:31:41 AM UTCgetEmailBody.error|
|Jan 15, 2020 11:31:41 AM UTCgetEmailBody.error|
|Jan 15, 2020 10:05:58 AM UTCgetEmailBody.error|
|Jan 15, 2020 10:05:58 AM UTCgetEmailBody.error|
|Jan 15, 2020 7:27:11 AM UTCgetEmailBody.error |
|Jan 15, 2020 6:35:28 AM UTCgetEmailBody.error |
|Jan 15, 2020 6:35:27 AM UTCgetEmailBody.error |
|Jan 15, 2020 6:35:25 AM UTCgetEmailBody.error |
|Jan 15, 2020 6:27:52 AM UTCgetEmailBody.error |
|Jan 15, 2020 6:27:50 AM UTCgetEmailBody.error |
|Jan 15, 2020 6:27:49 AM UTCgetEmailBody.error |
|Jan 15, 2020 3:03:56 AM UTCgetEmailBody.error |
|Jan 14, 2020 8:09:46 PM UTCgetEmailBody.error |
|Jan 14, 2020 8:04:32 PM UTCgetEmailBody.error |
|Jan 14, 2020 8:04:32 PM UTCgetEmailBody.error |
|Jan 14, 2020 7:41:28 PM UTCgetEmailBody.error |
|Jan 14, 2020 7:41:27 PM UTCgetEmailBody.error |
|Jan 14, 2020 7:32:02 PM UTCgetEmailBody.error |
|Jan 14, 2020 6:12:40 PM UTCgetEmailBody.error |
|Jan 14, 2020 6:12:39 PM UTCgetEmailBody.error |
|Jan 14, 2020 6:12:38 PM UTCgetEmailBody.error |
|Jan 14, 2020 4:39:02 PM UTCgetEmailBody.error |
|Jan 14, 2020 4:39:01 PM UTCgetEmailBody.error |
|Jan 14, 2020 2:56:22 PM UTCgetEmailBody.error |
|Jan 14, 2020 2:56:21 PM UTCgetEmailBody.error |
|Jan 14, 2020 2:56:21 PM UTCgetEmailBody.error |
|Jan 14, 2020 2:56:20 PM UTCgetEmailBody.error |
|Jan 14, 2020 2:29:51 PM UTCgetEmailBody.error |
|Jan 14, 2020 2:29:51 PM UTCgetEmailBody.error |
|Jan 14, 2020 12:52:43 PM UTCgetEmailBody.error|
|Jan 14, 2020 12:52:42 PM UTCgetEmailBody.error|
|Jan 14, 2020 12:52:42 PM UTCgetEmailBody.error|
|Jan 14, 2020 12:52:40 PM UTCgetEmailBody.error|
|Jan 14, 2020 12:38:34 PM UTCgetEmailBody.error|
|Jan 14, 2020 12:36:03 PM UTCgetEmailBody.error|
|Jan 14, 2020 12:36:02 PM UTCgetEmailBody.error|
|Jan 14, 2020 12:20:18 PM UTCgetEmailBody.error|
|Jan 14, 2020 12:20:18 PM UTCgetEmailBody.error|
|Jan 14, 2020 12:20:16 PM UTCgetEmailBody.error|
|Jan 14, 2020 12:19:48 PM UTCgetEmailBody.error|
|Jan 14, 2020 12:19:44 PM UTCgetEmailBody.error|
|Jan 14, 2020 12:19:43 PM UTCgetEmailBody.error|
|Jan 14, 2020 12:19:29 PM UTCgetEmailBody.error|
|Jan 14, 2020 12:17:47 PM UTCgetEmailBody.error|
|Jan 14, 2020 12:17:46 PM UTCgetEmailBody.error|
|Jan 14, 2020 12:17:45 PM UTCgetEmailBody.error|
|Jan 14, 2020 12:17:45 PM UTCgetEmailBody.error|
|Jan 14, 2020 12:17:35 PM UTCgetEmailBody.error|
|Jan 14, 2020 12:17:33 PM UTCgetEmailBody.error|
|Jan 14, 2020 12:17:33 PM UTCgetEmailBody.error|
|Jan 14, 2020 12:17:31 PM UTCgetEmailBody.error|
|Jan 14, 2020 12:17:31 PM UTCgetEmailBody.error|
|Jan 14, 2020 12:17:29 PM UTCgetEmailBody.error|
|Jan 14, 2020 12:17:29 PM UTCgetEmailBody.error|
|Jan 14, 2020 12:17:29 PM UTCgetEmailBody.error|
|Jan 14, 2020 12:17:28 PM UTCgetEmailBody.error|
|Jan 14, 2020 12:17:27 PM UTCgetEmailBody.error|
rudzon
on 16 Jan 2020
We have fixed the bug and it should be available. Depending on the release channel a customer is on; getting an updated build can take anywhere between 4-8 weeks
exextoc
on 26 Jan 2020
BTW, I've managed to reproduce this error:
{
name: "GenericResponseError",
message: "An internal error has occurred.",
code: 9020
}
Steps to reproduce:
- Subscribe to
Office.EventType.ItemChangedevent and try to fetch the email body usingOffice.context.mailbox.item.body.getAsyncevery time this event is triggered. - Pin the taskpane.
- Try to click on a few emails quickly. I get this error when I click on two or three items.
modestfake
on 10 Feb 2020
@exextoc I'm trying to create a customer facing statement for users that license our App and run into this issue. You mentioned that the fix is dependent on the release channel a customer is on. Are you implying this is a fix that needs to be added to each client or is the fix on the server side? Regardless, can you help me explain to them how they can determine when they will get the fix from Microsoft and, if possible, how they can get it even faster?
chrisecorcoran
on 10 Feb 2020
@exextoc would you be kind enough to reply to the above RE: the customer facing message?
chrisecorcoran
on 18 Feb 2020
@chrisecorcoran If you are referring to the issue posted by @anilreddyr7, the fix is already rolled out to Production. The issue posted by @modestfake appears to be different from the original issue.
exextoc
on 20 Feb 2020
@exextoc I am referring to the issue posted by @anilreddyr7 and I previously understood the fix was rolled out to production but my questions remain because of (my) confusion about the timing of the release (4-8 weeks). I need to understand more so I can provide our own customers with answers.
- How does the customer receive the fix (ie is it a client side update that depends on a release channel)?
- Can a customer opt to receive it earlier?
Thank you.
chrisecorcoran
on 20 Feb 2020
@chrisecorcoran
For Outlook Online, new fixes are deployed every Monday and deployment saturates to 100% by Friday. The fixes are available globally thereafter.
For highly critical issues, we do provide Hot Fixes which will reach the Customers earlier.
exextoc
on 24 Feb 2020
@exextoc thank you.
RE: the issue reported by @anilreddyr7 - thank you for confirming how updates roll out for Outlook online. I do have remaining questions above but will add here for more clarity.
- Is this a client side fix for desktop users and if so how do they get the update AND how can they get it sooner?
- If it is not a client side fix but the user uses desktop Outlook then how does their admin get the update?
Chris
chrisecorcoran
on 24 Feb 2020
This issue was reported for OWA and the fix went in OWA client.
exextoc
on 25 Feb 2020
Related issues
barisbikmaz
·
4Comments
dgrudenic
·
3Comments
Jarch09
·
3Comments
dimitri-bourreau
·
4Comments
ndeeH
·
5Comments
Most helpful comment
@exextoc I'm trying to create a customer facing statement for users that license our App and run into this issue. You mentioned that the fix is dependent on the release channel a customer is on. Are you implying this is a fix that needs to be added to each client or is the fix on the server side? Regardless, can you help me explain to them how they can determine when they will get the fix from Microsoft and, if possible, how they can get it even faster?