Teem incident

S2 - Outlook Plugin Log in Looping

Major Resolved View vendor source →

Teem experienced a major incident on May 14, 2025, lasting 2d. The incident has been resolved; the full update timeline is below.

Started
May 14, 2025, 04:07 PM UTC
Resolved
May 16, 2025, 04:58 PM UTC
Duration
2d
Detected by Pingoru
May 14, 2025, 04:07 PM UTC

Update timeline

  1. investigating May 14, 2025, 04:07 PM UTC

    We are currently investigating an issue with Teem. We will update you when we have more information.

  2. identified May 14, 2025, 06:58 PM UTC

    The issue has been identified and a fix is being implemented.

  3. identified May 14, 2025, 07:36 PM UTC

    The issue with the Plugin has been identified and a fix is being implemented. We will post another update at 6 PM CST. If you're experiencing this issue, please make sure you have followed these steps https://knowledge.eptura.com/Teem/Production_Information/Announcement/New_authentication_implementation_for_Teem_Outlook_plugin From there please reach out to support for help as there is a current workaround.

  4. identified May 14, 2025, 10:22 PM UTC

    The issue with the Plugin has been identified and a fix is being implemented. We will post another update tomorrow at 9 AM CST If you're experiencing this issue, please make sure you have followed these steps https://knowledge.eptura.com/Teem/Production_Information/Announcement/New_authentication_implementation_for_Teem_Outlook_plugin Once those steps have been followed if you try to login and are met with an infinite login loop please open an incognito window and log into your OWA instance and re-launch the Plugin. If you need assistance on how to do this or are encountering another error message please reach out to support for further troubleshooting.

  5. identified May 15, 2025, 02:07 PM UTC

    The issue with the Plugin has been identified and a fix is being implemented. We will post another update at 12 PM CST If you're experiencing this issue, please make sure you have followed these steps https://knowledge.eptura.com/Teem/Production_Information/Announcement/New_authentication_implementation_for_Teem_Outlook_plugin Once those steps have been followed if you try to login and are met with an infinite login loop please open an incognito window and log into your OWA instance and re-launch the Plugin. If you need assistance on how to do this or are encountering another error message please reach out to support for further troubleshooting.

  6. identified May 15, 2025, 05:31 PM UTC

    The issue with the Plugin has been identified and a fix is being implemented. We will post another update at 5 PM CST If you're experiencing this issue, please make sure you have followed these steps https://knowledge.eptura.com/Teem/Production_Information/Announcement/New_authentication_implementation_for_Teem_Outlook_plugin Once those steps have been followed if you try to login and are met with an infinite login loop please open an incognito window and log into your OWA instance and re-launch the Plugin. If you need assistance on how to do this or are encountering another error message please reach out to support for further troubleshooting.

  7. identified May 16, 2025, 12:19 AM UTC

    The issue with the Plugin has been identified and a fix is being implemented. We will post another update at 9 AM MST If you're experiencing this issue, please make sure you have followed these steps https://knowledge.eptura.com/Teem/Production_Information/Announcement/New_authentication_implementation_for_Teem_Outlook_plugin Once those steps have been followed if you try to login and are met with an infinite login loop please open an incognito window and log into your OWA instance and re-launch the Plugin. If you need assistance on how to do this or are encountering another error message please reach out to support for further troubleshooting.

  8. monitoring May 16, 2025, 02:37 PM UTC

    A fix has been implemented. We are moving into the Monitoring Phase for the next two hours. We appreciate your patience as our team worked diligently to provide a solution for this.

  9. resolved May 16, 2025, 04:58 PM UTC

    As we have not seen further service disruptions after the fix was implemented, we have moved to the Resolved Phase. Thank you for all the patience as we worked through this issue.