Open mkondadg opened 9 months ago
Hi @mkondadg, just to clarify, the timeout differences are happening when sending an email with an on-send add-in installed, is that correct?
yes @Adrian-MSFT , the timeout differences are happening when sending an email with an on-send add-in installed
@mkondadg can you please clarify in what platform is this issue? is this Outlook for the Web, new Outlook? Outlook for windows? all?
@JuaneloJuanelo this is for new outlook on windows. We tested addin deployed using native app and browser (both using same user account on which addin is deployed)
jsut for completeness. on traditional outlook for Windows this should fail immediatly, right?
In addition to the last question, are you using the ItemSend (on-send V1) feature or the Smart Alerts (on-send V2) feature?
@JuaneloJuanelo On traditional outlook, addin's will be disabled if COM sensor is already active. Below entry will disable new outlook addin and hence it will not fail in this case
<EquivalentAddins>
<EquivalentAddin>
<ProgId>prog-id-company</ProgId>
<Type>COM</Type>
</EquivalentAddin>
</EquivalentAddins>
@Adrian-MSFT we are using [Smart Alerts (on-send V2)]
Thanks for reaching out. This bug in our backlog but unfortunately we donot have nay timelines to share at this point. Internal tracking id- 246718
We also observed that "Smart Alert" is generated within 5 secs if addin doesnt respond quickly.
Provide required information needed to triage your issue
If Addin on webserver is unavailable, Outlook addin on browser timesout after 5 min but on native app, it timesout after 15 secs
Your Environment
Windows desktop Outlook You have Microsoft Outlook Version 1.2023.1018.300 (Production). Client Version is 20231027003.07 . Windows 10 Enterprise 21H2 19044.2006
Expected behavior
Addin timeout should be consistent on different browsers (chrome, firefox, edge, safari on mac) and native outlook app (windows, mac)
Current behavior
Outlook addin on browser timesout after 5 min but on native app, it timesout after 15 secs
Steps to reproduce
Deploy addin and make the webserver (where addin is hosted) down or Deploy addin where webserver URL is invalid in manifest.xml
Context
User experience is not consistent when addin is not available and user has to wait for very long time (5 min) to see the error