Outlook Web加载项错误通知显示异常：代码配置未生效求助

Let's troubleshoot why your error notification is incorrectly displaying as an info message. Here are the actionable steps to resolve this:

1. Verify the type Parameter (and Check for Edge Cases) #

While errorMessage is the documented valid value for error notifications in Office JS, some older Outlook Web builds have inconsistencies with this enum. Try switching to the shorthand "error" instead to see if that fixes the type mismatch:

Office.context.mailbox.item.notificationMessages.addAsync(
  "error-notification",
  { type: "error", message: "The add-in failed to process this message." }
);

2. Add an Async Callback to Catch Silent Failures #

Since addAsync runs asynchronously, the issue might be that the API call is failing silently, and Outlook is falling back to a default info notification. Add a callback to log any hidden errors:

Office.context.mailbox.item.notificationMessages.addAsync(
  "error",
  { type: "errorMessage", message: "The add-in failed to process this message." },
  (asyncResult) => {
    if (asyncResult.status === Office.AsyncResultStatus.Failed) {
      console.error("Notification failed to load: ", asyncResult.error);
    }
  }
);

Check your browser's developer console (F12) for error logs—this will reveal if the call is blocked due to permissions or timing issues.

3. Ensure You’re Calling the API at the Right Time #

If you trigger the notification before Office.context.mailbox.item is fully loaded, Outlook might ignore the specified type. Always wrap your notification code inside Office.onReady() to guarantee the mailbox item is available:

Office.onReady((info) => {
  if (info.host === Office.HostType.Outlook) {
    // Safe to access mailbox.item now
    Office.context.mailbox.item.notificationMessages.addAsync(
      "error",
      { type: "errorMessage", message: "The add-in failed to process this message." }
    );
  }
});

4. Rule Out Cache & Version Issues #

Older Outlook Web versions (especially those tied to legacy Exchange plans) may have limited support for notification types. Try:

• Testing in an incognito/private browser window to bypass cached data
• Updating to the latest Outlook Web version (check via Settings > About Outlook)

5. Confirm Add-in Permissions #

Restricted permission levels (like ReadItem) can limit access to notification APIs. Ensure your add-in uses the ReadWriteMailbox permission in its manifest file to unlock full functionality.

内容的提问来源于stack exchange，提问作者Shyam sundar shah