Monitoring - Apple released macOS 15.0.1 which “improves compatibility with third-party security software” that is the main cause for users experiencing Dialer issues who updated to 15.0.
The Salesloft team will continue to monitor this space for more updates.
Oct 09, 2024 - 10:40 EDT
Investigating - The Salesloft team has been informed that the most recent version of MacOS Sequoia (MacOS 15) is causing widespread issues with VPNs, antivirus software, and various web browsers which is also impacting users of the Dialer. Some users on MacOS 15 might experience dropped calls and other connectivity issues.
The Salesloft team is monitoring this closely with Apple and our technology partners for remediation. Our recommendation is not to update to the newest OS until an "all clear" is received and these widespread known issues with MacOS 15 are resolved.
We will continue to post updates as we receive them.
Sep 24, 2024 - 11:35 EDT
Resolved -
We've deployed a fix that has resolved Salesloft being unresponsive. Please refresh your browser to ensure the applied changes take effect.
Nov 15, 18:59 EST
Monitoring -
We’ve deployed a fix that has resolved the temporary outage. We’re monitoring to ensure the changes have the preferred impact. Continue to monitor the status page for additional updates.
Nov 15, 10:31 EST
Investigating -
We are investigating an issue with Salesloft being unresponsive. It has been reported that some customers may see a "503 Service Temporarily Unavailable" error. This seems to be impacting most of our customers. Our engineering team is currently working to identify what is causing this issue. Please continue to monitor our Status Page for additional updates.
Nov 15, 10:28 EST
Resolved -
We've deployed a fix that has resolved the Microsoft Teams Bot issues. While we recommend using the Teams API as the most secure and efficient method for capturing Teams meetings in Salesloft, the bot is now operational again and includes Active Speaker Detection.
Monitoring -
As of November 11th, the Microsoft Teams Bot has been updated and can now join and capture recordings from Teams meetings for any user lacking an active API connection to Microsoft Teams.
While we recommend using the Teams API as the most secure and efficient method for capturing Teams meetings in Salesloft, the bot is now operational again. Currently, the bot cannot identify individual speakers, so recordings will not include Active Speaker Detection in the transcript data. This functionality is slated for an upcoming release later this week.
Thank you for your patience and understanding while we work toward a more permanent answer.
Nov 11, 17:38 EST
Update -
We continue to investigate solutions to resolve this issue.
As of November 6th, to capture recordings, customers must move to our Teams API integration.
If the API Integration is not possible for your organization, we recommend manually recording in Microsoft Teams so that these meetings can retroactively be ingested into Salesloft or uploaded manually after completion until a more permanent solution is reached.
Thank you for your patience and understanding while we work toward a more permanent answer.
Nov 7, 09:34 EST
Investigating -
The Salesloft team is investigating reports of missing bots from meetings for a subset of customers using Microsoft Teams. Reporting users are not seeing the bot join their meetings and are unable to invite the bot to join manually.
We recommend utilizing the Teams API integrations to ensure your meetings are consistently being captured. Admin and user set up documentation are below.
Resolved -
This incident has been resolved.
Nov 7, 10:20 EST
Monitoring -
Google has approved the v1.3.11 of the Salesloft Chrome Extension. Please update your extension to the new version by clicking the 'reload' button on the extension. This will MS Teams and Zoom meeting links are being erased from invites after lofting. We will be monitoring this functionality before resolving this issue. Thank you for your patience.
Oct 30, 09:28 EDT
Update -
We are continuing to investigate this issue.
Oct 28, 12:04 EDT
Investigating -
Google updated the UI of their calendar over the weekend and there were several breaking changes that were occurred in the new Salesloft Chrome Extension as a result. The Salesloft Engineering team has already fixed several issues. To take advantage of those fixes, please go to the Salesloft Chrome extension and confirm that its on v1.3.10. If it isn't, you simply press the "Reload" button to update it to the latest available version.
One issue that will be addressed with the next version of the extension (v1.3.11) is that MS Teams and Zoom meeting links are being erased from invites after lofting. This fix has already been sent to Google for approval. This can take between a few hours and a couple of days. Please update the extension to v.1.3.11 as soon as it's available. Keep an eye on this status page for updates.
Oct 28, 11:57 EDT
Resolved -
We've deployed a fix that has resolved the Salesloft Connect issues. Please refresh your browser to ensure the applied changes take effect.
Nov 6, 17:17 EST
Monitoring -
We’ve deployed a fix that has resolved the Salesloft Connect Issues. Please update the Salesloft Connect Extension to version 1.3.14 to ensure the applied changes take effect. We’re monitoring to ensure the changes have the preferred impact. Continue to monitor the status page for additional updates.
Nov 5, 16:07 EST
Identified -
Engineering has identified the root cause and is working on a resolution. Please continue to monitor the status page for additional updates.
Nov 5, 16:00 EST
Investigating -
We are investigating various issues with the Salesloft Connect extension Version v1.3.13. It has been reported that customers are seeing functionality issues with the extension within their CRM and email accounts. Our engineering team is currently working to identify what is causing this issue. Please continue to monitor our Status Page for additional updates.
Nov 5, 15:39 EST
Resolved -
CRM Activities should now be successfully syncing without a delay. Customers who were impacted by the "503 Service Temporarily Unavailable" Salesforce activity error should be able to successfully retry those activities. This error was related to the ongoing Salesforce incident (https://status.salesforce.com/).
Nov 4, 11:13 EST
Monitoring -
Our engineering team has identified the issue with CRM activity logging. Users should be able to successfully retry activities with the 503 failure now. This is related to the SFDC ongoing incident (https://status.salesforce.com/). Any failing activities without an error should now be syncing, but may take a few hours to catch up. We’re monitoring to ensure all activities get successfully logged. Continue to monitor the status page for additional updates.
Nov 1, 16:52 EDT
Investigating -
We are investigating an issue with syncing activities to Salesforce which may related to a current Salesforce incident (https://status.salesforce.com/). It has been reported that some customers are seeing a 503 Service Temporarily Unavailable activity error. Some activities are not showing an error. This seems to be impacting some of our customers. Our engineering team is currently working to identify what is causing this issue. Please continue to monitor our Status Page for additional updates.
Nov 1, 15:03 EDT