Time: April 21, 2023, 5:44 p.m.

Status: Resolved

Update: We are pleased to inform you that the issues with our partner's API have been resolved. Our technical team has confirmed that the API is now functioning as expected, and all services relying on it should now be back to normal. We understand that this issue may have caused inconvenience and frustration, and we sincerely apologize for any negative impact it may have had on your experience. We strive to provide reliable and uninterrupted services, and we appreciate your patience and understanding while we worked to resolve this issue. If you continue to experience any problems or have any questions, please do not hesitate to contact our support team for further assistance. Thank you for your understanding.

Time: April 21, 2023, 4:23 p.m.

Status: Identified

Update: We regret to inform you that one of our CRM service partners is currently experiencing an API issue that is impacting a subset of our clients. This has resulted in some users being unable to access certain features and functions of our platform, and may also cause some of our services to be slow or non-responsive. Our technical team is actively working with the partner to resolve the issue as soon as possible. We apologize for any inconvenience this may be causing and appreciate your patience and understanding during this time. We will provide updates on the progress of this issue as soon as we have more information. In the meantime, if you have any questions or concerns, please do not hesitate to reach out to our support team. Thank you for your understanding.

Time: April 24, 2023, 10:37 p.m.

Status: Postmortem

Update: ## Summary We recently experienced intermittent outages with the Workflow API, which caused some disruptions to the connectivity of PopFlows. As a result, some PopFlow functionality \(such as ScreenPops, Data Retrieval and Lookups, and General Use\) was impacted. ## What was impacted * PopFlow functionality \(Ex: ScreenPops, Data Retrieval and Lookups, General Use\) ## Remediation We discovered a limitation in the scalability of our Workflow API. ‌ To prevent any future outages, we have implemented new scaling processes that will help us manage our shared resources more effectively and ensure that our services remain stable. ‌ We apologize for any inconvenience this may have caused and want to assure you that we are working hard to improve our systems to provide you with the best possible service. If you have any questions or concerns, please don't hesitate to reach out to us.

Time: April 21, 2023, 12:50 a.m.

Status: Resolved

Update: As mentioned earlier, we're happy to inform you that all systems are now functioning normally, and you should be able to use all our services without any issues. Our engineers have been monitoring the situation closely, and we're moving this issue to "resolved". We apologize for any inconvenience this incident may have caused, and we appreciate your patience and understanding throughout this time. We want to assure you that we take any disruptions to our service very seriously, and we're committed to conducting a thorough review of our systems and processes to prevent similar issues from occurring in the future. If you have any questions or concerns, please don't hesitate to contact our support team, who will be more than happy to assist you.

Time: April 21, 2023, 12:02 a.m.

Status: Monitoring

Update: Hello everyone, We're happy to report that the issues we were experiencing earlier have now been resolved, and all systems are functioning normally. Our team has been working around the clock to identify and fix the root cause of the issue, and we're confident that we've addressed the underlying problem. While we're pleased to have resolved this issue, we want to assure you that we'll be continuing to monitor our systems closely and investigate what led to the issue in the first place. Our goal is to prevent any similar issues from occurring in the future, and we're committed to providing you with the best possible service. We apologize for any inconvenience this incident may have caused, and we appreciate your patience and understanding. If you have any questions or concerns, please don't hesitate to contact our support team, who will be happy to assist you.

Time: April 20, 2023, 10:10 p.m.

Status: Identified

Update: We want to inform our users that we are currently experiencing issues with our Workflow API, and our team is actively working on resolving these problems. We apologize for any inconvenience this may cause. As of now, we are still in the process of identifying the root cause of the issues, and our team is working diligently to restore the API's functionality as soon as possible. We will continue to provide updates as we make progress towards resolving this matter. Thank you for your patience and understanding

Time: April 20, 2023, 10:03 p.m.

Status: Monitoring

Update: After monitoring the services, we have verified that the connectivity has been reinstated. Our team of engineers will keep an eye out for any potential service disruptions.

Time: April 20, 2023, 9:39 p.m.

Status: Investigating

Update: We are currently experiencing an issue with the Workflow API. Consequently, users might will not be able to use PopFlows. Our engineers are investigating the matter.

Time: Dec. 13, 2022, 6:39 p.m.

Status: Postmortem

Update: ## Summary OpenMethod Services were unavailable during an outage from our service provider. The outage was confined to servers and services in the Ohio East cloud region.  ## What was impacted * Connectivity, access, and functionality to OpenMethods products and services. * Harmony Media Bar: Loading and display of the media bar. * PopFlow: Loading screen pops and workflow activities. ## Remediation The resolution was from our service provider, which brought services back to a functional state. ‌ **Current Action Plans:** * OpenMethods has introduced additional geographical redundancy to our clients on the latest product release of Experience Cloud 6.10\+.  * _Note: these changes are currently for PopFlow services only._  ‌ **Future Planning:** * The following are in planning: * Additional geographical redundancy across the OpenMethods products & services.

Time: Dec. 5, 2022, 9:41 p.m.

Status: Resolved

Update: This incident has been resolved.

Time: Dec. 5, 2022, 9:23 p.m.

Status: Identified

Update: We are continuing to monitor and will resolve this incident when it appears all functionality has been restored.

Time: Dec. 5, 2022, 9:22 p.m.

Status: Identified

Update: We are currently experiencing an intermittent issue with OpenMethods applications that may result in users may have limited or no functionality. One of our product partners is experiencing an issue. This issue has been marked as resolved on their end, but it may take some time before users have restored functionality. (https://status.aws.amazon.com/rss/internetconnectivity-us-east-2.rss)

Time: Nov. 7, 2022, 10:38 p.m.

Status: Resolved

Update: This incident has been resolved. The root cause is under investigation. We apologize for any inconvenience this incident may have caused.

Time: Nov. 7, 2022, 10:21 p.m.

Status: Monitoring

Update: A fix has been implemented and we are monitoring the results.

Time: Nov. 7, 2022, 10:01 p.m.

Status: Investigating

Update: We are continuing to investigate this issue.

Time: Nov. 7, 2022, 9:02 p.m.

Status: Investigating

Update: We are currently experiencing an issue with the Workflow API. Consequently, users might not be able to execute PopFlow. Our engineers are investigating the matter.

Time: Nov. 4, 2022, 10:56 p.m.

Status: Resolved

Update: We've identified an issue with Desktop Notifications. Users may receive a message "Uh oh ... no parent frame detected" instead of a standard desktop notification. <b>A workaround has been documented to resolve the issue. <a href="https://docs.openmethodscloud.com/en_US/tech-security-alerts/desktop-notification-workaround">View the workaround here</a.>.<b/> A fix to this issue has been identified and will be delivered and released in our next maintenance window.

Time: Nov. 4, 2022, 9:46 p.m.

Status: Identified

Update: We are currently experiencing an issue with the PopFlow Desktop Notifications. Consequently, users may receive a message "Uh oh ... no parent frame detected" in place of a standard desktop notification. Our engineers are investigating the matter.