Update - We would like to inform that the workaround for installing the Live Assist is failing to authorize now via the API. Our Development Team is closely working with Microsoft to resolve the issue. Should there be another workaround available before the issue has been totally resolved, we will share it also.
For further clarification, you can reach our technical support by emailing support@liveassistfor365.com.
Dec 16, 2024 - 15:27 UTC
Update - As the recode to work with our third-party's new API is still ongoing, we would like to share here an article for the workaround we mentioned to successfully install/provision the Live Assist for Microsoft Dynamics 365 (LAD365).
If you need further assistance, please raise a request by emailing our technical support at support@liveassistfor365.com.
Dec 12, 2024 - 08:48 UTC
Update - As the recode to work with our third-party's new API is still ongoing, we would like to share here an article for the workaround we mentioned to successfully install/provision the Live Assist for Microsoft Dynamics 365 (LAD365).
If you need further assistance, please raise a request by emailing our technical support at support@liveassistfor365.com.
Dec 03, 2024 - 04:14 UTC
Identified - We have identified the cause of the issue where some partner's APIs have changed and so our provisioning broke. We have a temporary workaround in place while we recode to work with their new APIs.
If you are having an issue with installing Live Assist in your Dynamics, please raise a request by emailing our technical support at support@liveassistfor365.com.
Nov 19, 2024 - 13:32 UTC
Update - We continuously investigate this issue with our partner's engineering team to find the root cause. We appreciate your understanding. If it's urgent or you really need to install Live Assist in your Dynamics, please raise a request by emailing our technical support at support@liveassistfor365.com.
Oct 29, 2024 - 01:16 UTC
Update - We are continuing to investigate this issue with our partner where the installation of the Live Assist from the Microsoft AppSource may fail. Alternatively, you can install the Live Assist application from the Power Platform admin center > Resources (on the left pane) > Dynamics 365 apps > Live Assist for Dynamics 365 powered by LivePerson (with "Configured" status) > click "Manage". For more assistance, please contact Live Assist Technical Support at support@liveassistfor365.com.
Sep 13, 2024 - 06:52 UTC
Update - We are investigating this issue further and with our partner.
Sep 06, 2024 - 05:52 UTC
Update - We are continuing to investigate this issue.
Aug 30, 2024 - 00:03 UTC
Investigating - We have identified a potential issue with LAD365 service onboarding. We are currently investigating a provisioning issue for intermittent issues with the onboarding of Live Assist . Our engineers are actively investigating this issue. We'll post updates as soon as we have more information.
Aug 29, 2024 - 16:58 UTC
Resolved -
Third-party dependency errors are no longer being detected, as the underlying issues have been resolved. Our services are now operating normally. Should you continue to experience any problems, please reach out or email our Teachnical Support (support@liveassistfor365.com) for assistance.
Oct 21, 01:01 UTC
Monitoring -
The incident related to AWS has been fully resolved and are observing early signs of improvement across some of its impacted services; however, full recovery has not yet been achieved. Correspondingly, gradual improvements are now seeing in the service performance. Our third-party teams are continuously validating system functionality to ensure platform health and stability. We will continue to monitor the situation closely and provide further updates as recovery progresses.
Oct 21, 00:37 UTC
Investigating -
Investigating - Our third-party service provider is investigating an issue affecting their automated messaging system. Automatic messages may not be sent via the Controller Bot, which could prevent dependent solutions—such as Parking Lot Bots, FaaS, and other features—from triggering as expected. Early indications suggest a potential third-party issue, possibly linked to an ongoing AWS outage. Their engineering team is actively working to resolve the issue. We will provide update as soon as we receive additional information from our provider.
Oct 20, 22:08 UTC
Resolved -
Engineering teams performed a service restart that resolved the reported issue. Subsequent checks have confirmed the system’s health and stability. Following the restart, conversation builder bot messages are successfully going through to consumers. System is fully recovered
Oct 20, 14:16 UTC
Update -
Engineering teams will perform a restart to services related to Conversation Builder in an attempt to mitigate the reported behavior. Following the restart, you may observe up to 10 minutes of platform instability—you may observe the "Please wait while the Conversational Cloud attempts to reconnect" error message.
Oct 20, 13:20 UTC
Investigating -
Our third-party service provider is currently experiencing technical issues affecting Conversation Builder bots. As a result, bots may not respond in conversations or route them correctly.
Our engineers have identified a potential issue with connectivity and message delivery and are fully engaged in investigating the matter. We understand how important this service is to you and will provide updates as soon as more information becomes available.
Oct 20, 11:52 UTC
Resolved -
Engineering teams implemented a change that resolved the reported issue. Subsequent checks have confirmed the system’s health and stability. Incident Resolved
Oct 15, 13:15 UTC
Update -
We are continuing to investigate this issue.
Oct 15, 12:51 UTC
Investigating -
Our third-party service provider is currently experiencing technical issues affecting Conversational Builder. As a result, users may be unable to load the tool, access existing bots, or make modifications.
Please note that bots already deployed remain fully operational and are not impacted by this issue.
Our engineering teams are actively working with the provider to resolve the problem as soon as possible.
Oct 15, 12:50 UTC