Outlook intermittently does not launch Add-In when clicked

Hi @Douglas Riggs

Thank you for sharing your concerns.

To better address the issue, could you please provide a bit more information on the following questions: 

Does this issue happen to all users in your organization, or only to some specific users? 

Are there any recent changes to your environment? 

In the meantime, you could try to: 

• Refresh the Outlook Web page (F5) when the button stops responding. 
• Clear your browser cache or try in Incognito/Private mode. 
• Test with a different browser. 

Please let me know the results after trying the workarounds above to better address this issue. 

Please understand that our initial reply may not always immediately resolve the issue. However, with your help and more detailed information, we can work together to find a solution. 

Note: Please follow the steps in [our documentation] to enable e-mail notifications if you want to receive the related email notification for this thread. 

Based on the available information, focus on validating and hardening the add-in’s manifest and JavaScript for event-based behavior, and then gathering more diagnostics from affected users.

1. Validate manifest and runtime mapping

• Ensure the manifest correctly references the HTML/JavaScript entry point for the add-in pane via SourceLocation (add-in-only manifest) or "extensions.runtimes.code.page" (unified manifest).
• Ensure the <Runtimes> element or "extensions.runtimes.code" property correctly points to the file that contains the event handlers.
• Confirm that the JavaScript file used by Outlook on the web is the one that actually initializes the UI and handlers for the add-in.

2. Ensure Office.actions.associate is used correctly If the add-in uses event-based handlers (On-send, On-new-compose, spam-reporting, etc.), verify that the JavaScript file:

• Calls Office.actions.associate for each event handler name declared in the manifest so that Outlook can map the manifest action to the correct JavaScript function.
• Example:

    Office.actions.associate("onNewMessageComposeHandler", onNewMessageComposeHandler);
  

If this mapping is missing or incorrect, Outlook may silently fail to invoke the handler for specific items, which can appear as “nothing happens” when the add-in is clicked.

3. Check JavaScript compatibility and bundling

• If the same JavaScript bundle is used across Outlook on the web, classic Outlook on Windows, and new Outlook, ensure the code is compatible with the supported ECMAScript level for the oldest target (for classic Windows clients prior to Version 2403, this is ECMAScript 2016 and earlier).
• Avoid patterns that can cause add-ins to time out or fail to load in those environments (for example, async/await and certain operators in older classic clients). If there is a single shared bundle, subtle runtime errors can manifest intermittently per item.
• If using webpack or another bundler, ensure the dev/build configuration serves static files and does not inject incompatible runtime code into the bundle that Outlook on the web relies on.

4. Narrow down item-specific conditions Because the issue is item-specific (fails on one message, works on another), collect details from affected users for failing items:

• Message type (e.g., specific folder, shared mailbox, or special item type).
• Any classification, sensitivity labels, or rights management applied.
• Whether the item is in a state that might affect add-in activation (e.g., protected content, special message class). Compare these items to working ones to identify patterns that might affect activation rules or runtime behavior.

5. Add instrumentation and logging

• Add client-side logging in the add-in’s JavaScript to capture when the add-in frame loads, when initialization runs, and any exceptions.
• Surface a minimal diagnostic UI (for example, a simple “loaded” indicator) so users can confirm whether the add-in frame is loading but failing later, or not loading at all.

6. If the issue persists

• After validating the manifest, runtime mapping, and JavaScript compatibility, and after adding logging, if the add-in still intermittently fails only in Outlook on the web, collect session details and logs from affected users and open a support case so engineering can review backend telemetry for the tenant.

References:

• Troubleshoot event-based and spam-reporting add-ins