Salesloft driftsforstyrrelser

1. 13. juli 2026 kl. 14.40 UTCinvestigating

   Vi undersøger et problem med Microsoft Team Integration. Det er blevet rapporteret, at nogle kunder ikke er i stand til at forbinde til Teams Integration i Salesloft. Vores ingeniørhold arbejder i øjeblikket på at identificere, hvad der forårsager dette problem. Fortsæt med at overvåge vores statusside for yderligere opdateringer.

2. 13. juli 2026 kl. 21.36 UTCidentified

   Engineering har identificeret årsagen og arbejder på en resolution. Fortsæt med at overvåge statussiden for yderligere opdateringer.

3. 14. juli 2026 kl. 11.44 UTCresolved

   Vi har indsat en rettelse, der har løst problemerne med at forbinde Microsoft Teams i Salesloft. Opdater din browser for at sikre, at de anvendte ændringer træder i kraft.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 2. juli 2026 kl. 18.39 UTCinvestigating

   Vi undersøger et problem med Messenger / SMS-funktionen er nede. Det er blevet rapporteret, at Messenger ikonet er grayed ud med fejlen "Messaging ikke aktiveret". Dette synes at påvirke nogle af vores kunder. Vores ingeniørhold arbejder i øjeblikket på at identificere, hvad der forårsager dette problem. Fortsæt med at overvåge vores statusside for yderligere opdateringer.

2. 2. juli 2026 kl. 19.01 UTCmonitoring

   Vi har sat en løsning på problemerne med Messenger. Log ud og tilbage i for at sikre, at de anvendte ændringer får virkning. Vi overvåger, at ændringerne har den foretrukne virkning. Fortsæt med at overvåge statussiden for yderligere opdateringer.

3. 3. juli 2026 kl. 09.30 UTCresolved

   Den indsatte en rettelse har løst problemerne med Saleslov Messenger.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 22. juni 2026 kl. 18.29 UTCinvestigating

   We are currently investigating an issue where Drift bot replies/messages are not immediately displaying to end users and appearing only after page refresh.

2. 22. juni 2026 kl. 20.19 UTCinvestigating

   We are continuing to investigate this issue.

3. 22. juni 2026 kl. 20.22 UTCidentified

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

4. 22. juni 2026 kl. 20.34 UTCresolved

   This incident has been resolved.

1. 19. juni 2026 kl. 11.19 UTCinvestigating

   We are currently investigating an issue where users are seeing a message saying: "The editor will be disabled in the near future because the license key has expired." in the email draft panel. The ability to draft and send emails remains functional and we will update this page with more information once we have identified the cause. We apologise for any inconvenience.

2. 19. juni 2026 kl. 15.41 UTCidentified

   We have successfully identified the issue causing the errant "the editor will be disabled in the near future because the license key has expired" banner. Engineering is currently implementing a fix to resolve the matter. We are monitoring the situation closely and will provide another update as soon as we have it. Thank you for your patience!

3. 22. juni 2026 kl. 09.07 UTCidentified

   Engineering has identified the root cause and is working on implementing a fix for the errant "The editor will be disabled in the near future because the license key has expired" banner displaying within the email compose window in Salesloft. As noted earlier, this is a visual error only. Teams can continue to draft and send emails as normal without interruption. We will update this page once the banner has been successfully removed.

4. 22. juni 2026 kl. 22.00 UTCresolved

   Our Engineers have deployed a fix for the banner users were seeing in the email draft panel. Please refresh your browser to ensure the applied changes take effect.

1. 12. maj 2026 kl. 14.02 UTCinvestigating

   We are investigating reports of unresponsiveness within the platform affecting a subset of customers. Our engineering team is working to identify the root cause. Please continue to monitor this page for further updates.

2. 12. maj 2026 kl. 15.18 UTCmonitoring

   Our Engineers have deployed a fix to resolve the platform unresponsiveness. Please log out and back in 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.

3. 14. maj 2026 kl. 15.06 UTCresolved

   We've deployed a fix that has resolved some unresponsiveness within the platform. Please refresh your browser to ensure the applied changes take effect.

1. 14. april 2026 kl. 14.41 UTCinvestigating

   We are currently investigating reports of intermittent issues affecting our dialer and email services. Our team is working to identify the root cause, and we will provide an update as soon as more information is available.

2. 14. april 2026 kl. 14.47 UTCidentified

   Engineering has identified the root cause and is working on a resolution. Please continue to monitor the status page for additional updates.

3. 14. april 2026 kl. 16.09 UTCmonitoring

   We’ve deployed a fix that should resolve the email and dialer issues. Please refresh your browser 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.

4. 14. april 2026 kl. 22.23 UTCresolved

   We've deployed a fix that has resolved the email and dialer issues. Please refresh your browser to ensure the applied changes take effect.

1. 13. april 2026 kl. 20.14 UTCinvestigating

   We are currently investigating reports of intermittent issues affecting our dialer and email services. Our team is working to identify the root cause, and we will provide an update as soon as more information is available.

2. 13. april 2026 kl. 20.45 UTCmonitoring

   The dialer and email issues have been resolved. We are monitoring to ensure performance remains stable. You should now be able to use these services as expected.

3. 13. april 2026 kl. 23.00 UTCresolved

   We've deployed a fix that has resolved the dialer and email issues. Please refresh your browser to ensure the applied changes take effect.

1. 12. marts 2026 kl. 17.12 UTCidentified

   There’s currently an issue where users are receiving a permissions error when attempting to import records via our Chrome extension. Our engineering team has identified the root cause and is working on developing a fix. Please continue to monitor the status page for additional updates.

2. 16. marts 2026 kl. 23.19 UTCinvestigating

   Our Engineering team has identified the cause and is working on a fix as a top priority for the various extension issues. We will provide further updates as soon as more information is available. Please continue to monitor the status page for the latest updates. Thank you for your continued patience.

3. 17. marts 2026 kl. 14.07 UTCmonitoring

   We’ve deployed a fix to resolve the extension importing and Lofting issues. Please update Salesloft Connect to version V1.7.6 and refresh Chrome to ensure the changes take effect. We’re monitoring to ensure the changes have the preferred impact. Continue to monitor the status page for additional updates.

4. 18. marts 2026 kl. 14.00 UTCresolved

   We've deployed a fix that has resolved the extension issues. Please update Salesloft Connect to version V1.7.6 and refresh Chrome to ensure the changes take effect.

1. 9. marts 2026 kl. 11.25 UTCinvestigating

   We are investigating reports of increased latency within the platform affecting a subset of customers. Our engineering team is working to identify the root cause. Please continue to monitor this page for further updates.

2. 9. marts 2026 kl. 14.34 UTCmonitoring

   Our engineers have deployed a fix to address the latency and performance issues that were impacting a subset of customers. We are seeing performance return to normal levels and will continue to monitor the system closely to ensure the changes have the intended effect.

3. 9. marts 2026 kl. 18.27 UTCresolved

   This incident has been resolved.

1. 23. februar 2026 kl. 16.05 UTCinvestigating

   We are investigating an issue with general slowness within the platform. Our engineering team is currently working to identify what is causing this issue. Please continue to monitor our Status Page for additional updates.

2. 23. februar 2026 kl. 17.40 UTCidentified

   Engineering has identified the root cause and is working on a resolution. Please continue to monitor the status page for additional updates.

3. 23. februar 2026 kl. 18.02 UTCmonitoring

   Our Engineers have deployed a fix to resolve the overall platform slowness. Please log out and back in 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.

4. 23. februar 2026 kl. 20.36 UTCidentified

   After initial improvements, we’re now seeing increased latency again in the app. Our team is investigating and implementing additional mitigation. We’ll provide another update within the next 3 hours, or sooner if the issue is resolved.

5. 23. februar 2026 kl. 21.42 UTCmonitoring

   We identified an issue with an internal networking component which caused the slowness. We mitigated the issue by scaling up additional infrastructure. Our metrics show that the latency has returned to normal levels. We continue to the monitor performance and will resolve this incident after 24 hours, once the performance is stable.

6. 24. februar 2026 kl. 21.58 UTCresolved

   This incident has been resolved.

1. 10. februar 2026 kl. 17.45 UTCinvestigating

   We are currently investigating reports where the bot is firing after a delay or is stalling in the middle of a conversation.

2. 10. februar 2026 kl. 20.53 UTCmonitoring

   We have identified the root cause and deployed a fix. We will continue to monitor the situation to ensure complete stability.

3. 10. februar 2026 kl. 20.54 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 10. februar 2026 kl. 22.01 UTCresolved

   This incident has been resolved.

1. 4. februar 2026 kl. 19.42 UTCinvestigating

   We are investigating an issue where playbook flows are stopping prematurely causing routing to not occur.

2. 4. februar 2026 kl. 19.43 UTCinvestigating

   We are continuing to investigate this issue.

3. 6. februar 2026 kl. 18.18 UTCresolved

   This incident has been resolved.

1. 2. februar 2026 kl. 18.59 UTCinvestigating

   We are currently investigating reports where users Lofting emails from Outlook are finding the message body replaced with the text "Undefined."

2. 3. februar 2026 kl. 23.08 UTCresolved

   We have successfully deployed a fix for the issue where Lofted emails sent via the Outlook Extension were arriving with the body content replaced by the word "Undefined." Thank you for your patience.

1. 27. januar 2026 kl. 15.00 UTCinvestigating

   We are currently investigating reports that Salesforce extension buttons are not appearing as expected within the browser extension. Our engineering team is currently looking into the matter to restore full functionality.

2. 28. januar 2026 kl. 14.20 UTCinvestigating

   This incident is now considered resolved. Thank you for your patience

3. 28. januar 2026 kl. 15.15 UTCresolved

   This incident is now considered resolved. Thank you for your patience

1. 15. januar 2026 kl. 19.36 UTCinvestigating

   We are investigating an issue with Zoom links not being automatically added to meeting invites booked through Salesloft meeting links. 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.

2. 16. januar 2026 kl. 14.53 UTCidentified

   Engineering has identified the root cause and is working on a resolution. Please continue to monitor the status page for additional updates.

3. 16. januar 2026 kl. 14.53 UTCidentified

   We are continuing to work on a fix for this issue.

4. 20. januar 2026 kl. 15.11 UTCresolved

   Our Engineers have deployed a fix that has resolved the issue with missing Zoom links in some calendar invites. Please refresh your browser to ensure the applied changes take effect.

1. 10. december 2025 kl. 21.40 UTCinvestigating

   Our Engineers are investigating an issue where the Deals page is not loading. We will provide an update as soon as we have more information.

2. 11. december 2025 kl. 09.04 UTCresolved

   The outstanding issue with Deals not loading for a certain subset of customers has been resolved.

1. 8. december 2025 kl. 10.50 UTCinvestigating

   We are currently investigating an issue affecting the Account and People pages in Salesloft. Users are encountering "Page Not Found" or "Page Doesn't Exist" errors when clicking the Salesforce icon to view the record in their CRM. Our engineering team is actively working to identify the root cause. We will provide another update as soon as we have more information.

2. 11. december 2025 kl. 14.04 UTCinvestigating

   The Salesloft team continues to investigate the root cause of this error. It is a top priority for the team, and we will post more updates as we work toward a permanent solution. Thank you for your continued patience while we investigate.

3. 11. december 2025 kl. 18.53 UTCidentified

   The Salesloft team has identified the root cause of this issue and is currently working on the fix. We will have more updates as this is correct. Thanks again for bearing with us while we work to address.

4. 12. december 2025 kl. 19.20 UTCmonitoring

   A fix has been implemented, and customers are confirming that the errors triggered by clicking the Salesforce link icons are resolved. We will continue monitoring to ensure the issue remains fully resolved.

5. 12. december 2025 kl. 22.53 UTCresolved

   This incident has been resolved. Thank you for your patience as we worked to address it.

1. 18. november 2025 kl. 13.27 UTCidentified

   Salesloft is receiving reports from customers that the Global Cloudflare Outage is impacting some aspects of their Salesloft experience, including logging in via SSO and tracked links. We will continue to monitor Cloudflare's status page as their systems come back online. https://www.cloudflarestatus.com/incidents/8gmgl950y3h7

2. 18. november 2025 kl. 14.45 UTCmonitoring

   The Cloudflare team has sent an update that a fix has been implemented and they believe the incident is now resolved. We are continuing to monitor for errors to ensure all services are back to normal. If your team is having trouble with SSO, please try again.

3. 19. november 2025 kl. 13.24 UTCresolved

   This incident has been resolved.

1. 17. november 2025 kl. 15.41 UTCidentified

   A subset of customers have reported that Zoom links are failing to auto-populate in calendar invites when booking meetings through Salesloft. Engineering has identified the root cause and is working on a resolution. Please continue to monitor the status page for additional updates. In the meantime, affected users will need to manually add a Zoom link to their calendar invites.

2. 20. november 2025 kl. 16.22 UTCresolved

   Our Engineers have deployed a fix for this issue and Zoom links should be auto-populating in meeting invites again. Please refresh your browser to ensure the applied changes take effect.

1. 11. november 2025 kl. 17.20 UTCinvestigating

   We are currently investigating an issue where the Conversation Intelligence bot for Microsoft Teams successfully joins scheduled meetings, but the recording does not process as expected afterward. Impacted users may see an error message similar to: “Recording skipped: Recording has no audible words to be transcribed.” The issue appears to affect a subset of customers and meetings at this time. Our engineering team is actively investigating the root cause. We will provide an update as soon as we have more information.

2. 11. november 2025 kl. 21.54 UTCmonitoring

   A fix was deployed to production around 4:00 PM Eastern, and new meetings are now recording and processing correctly. We’ve also added enhanced error reporting to help us detect and resolve similar issues more quickly in the future. Our team identified an issue that caused the Conversation Intelligence bot to join meetings but fail to capture audio, resulting in missed recordings. Please note that, due to the nature of the recording process, previously affected meetings cannot be recovered or reprocessed. We apologize for the disruption this may have caused. We are currently monitoring to ensure the issue has been fully resolved.

3. 12. november 2025 kl. 16.22 UTCresolved

   This incident has been resolved.