Orum Status

Resolved: The challenge has been resolved and users are able to join Salesfloor rooms as expected.

Monitoring: A fix has been implemented and we are monitoring system. Our engineering team has verified that Salesfloor room access has been restored and will continue to observe system metrics.

Identified: We have identified the cause of the behavior and are currently validating the path forward to address the challenge. We will continue to provide additional updates as research continues.

Identified: We have identified the cause of the behavior and are implementing a fix. This is related to a 3rd party API interaction. We are working toward a resolution and will provide further updates as they become available.

Investigating: Investigating - We are actively investigating reports of errors when users attempt to join Salesroom rooms within Orum. We will provide more information as soon as it becomes available.

Resolved: System metrics have returned to normal. The fix has been deployed and we have verified that dialing is functioning as expected.

Identified: We have identified the cause of the behavior and are implementing a fix. We are currently deploying the solution and expect dialing services to be restored shortly.

Investigating: We are actively investigating reports of users being unable to place dials within the Orum platform. Our team is working to identify the cause of this behavior and we will provide an update shortly.

Resolved: We have concluded our active monitoring and are marking this challenge as resolved. Please ensure your session is fully synchronized with our backend fix-- we strongly recommend that all users log out and log back into Orum if they have not already done so since 930a PT today (4/1). If prompted with a Salesforce security warning or approval screen, please click "Allow" to ensure your connection is optimized.

Monitoring: Orum is exhibiting expected behavior once users have logged out & back in. We will continue active monitoring for another hour. If you are an SFDC-integrated user and have not logged out / back in after 930a PT, we recommend doing so. If prompted with a Salesforce security warning, please click "Allow".

Monitoring: We continue monitor the metrics for the SFDC-integrated challenge from earlier. If users have not done so since 930a PT, we recommend performing a logout and login cycle to synchronize their Orum session. If a Salesforce security warning or approval prompt appears, please click "Allow" to restore full list-loading functionality.

Monitoring: As we continue to monitor, we strongly recommend a logout/login cycle for all SFDC-integrated users if you have not done so already AFTER ~930a PT. If prompted with a Salesforce security warning or approval screen, please click "Allow" to ensure your connection to the Orum platform is fully synchronized.

Monitoring: We are continuing to monitor. To all SFDC-integrated users: please log out and log back into the Orum platform if you have not already done so. If prompted with a Salesforce security warning or approval screen, please click "Allow" to restore full functionality. This will help prevent any undesired downstream effects

Monitoring: We have identified the cause of the behavior and our engineering team has taken additional action on the backend to remediate the technical challenge. As part of this process, you may see a Salesforce approval screen or a "security warning" when logging back into the Orum platform. We want to clarify that no changes have been made to your permission sets or security configurations. This is a standard notification from the Salesforce side following our recent system updates. To resume your work, you can confidently click "Allow." This will restore your list loading functionality and ensure Orum operates as expected.

Monitoring: We continuing to monitor. All SFDC-integrated users are advised to log out and back in to Orum if they have not already done so.

Identified: Engineering has performed additional backend remediation. All SFDC-integrated users are required to log out and log back into Orum to ensure these changes take effect.

Identified: We have identified the cause of the behavior. Users experiencing challenges loading Salesforce lists should log out and log back into Orum to restore functionality.

Investigating: We are actively investigating reports of a challenge where users are unable to load Salesforce lists within Orum. Our engineering team is currently researching the root cause and we will provide an update shortly.

Resolved: Our active monitoring has concluded. The Outreach API error behavior has been fully resolved and all Orum integration services are operating as expected.

Monitoring: Outreach has confirmed their hotfix is live, and we are seeing metrics return to expected levels. We will continue to observe the platform to ensure a full recovery.

Identified: Outreach has identified the issue and deployed a fix to address the API errors. We are currently working to ensure all Orum services resume normal operation and will provide an update once we move into the monitoring phase.

Investigating: Outreach support is continuing to review the reported API connectivity symptoms. Our engineering team is in active contact with their technical department. We will provide another update within an hour or as soon as we receive more information from their team.

Investigating: We are actively investigating reports of connectivity challenges between Orum and Outreach. Our team is working with Outreach to identify the root cause of these API errors. We will provide further updates within an hour or as we learn more

Investigating: Investigating - We are actively investigating reports of challenges with the Outreach integration. We are currently working with Outreach's technical team to research the root cause of this behavior. Further updates will be provided as soon as more information is available.