Email & Mailboxes
System delivery notifications no longer misidentified as lead replies. Certain system emails — such as Google non-delivery reports — could previously be detected as a reply from a lead, changing the conversation status. These are now correctly recognized as system messages and no longer affect lead status or automation flow.
Improved bounce detection for SMTP mailboxes. Bounced emails were not always detected for mailboxes connected via SMTP, which meant sequences could continue sending to invalid addresses. This is now fixed.
Note: some older conversations may retroactively move to "bounced" status when the next email in the sequence is attempted — this is expected behavior as the system now correctly identifies previously missed bounces.
Fixed "No known authentication mechanisms supported" error. This error appeared when connecting older custom mailboxes that only support the AUTH LOGIN authentication method. These mailboxes now connect successfully.
Improved email sync resilience. We added multiple safeguards to prevent email synchronization from stalling:
Tasks that hang during processing now recover automatically instead of blocking the queue
A rare issue where IMAP operations could block sync indefinitely (bypassing the standard timeout) has been resolved
Added backend monitoring for mailbox errors to detect and respond to issues faster
SMTP connection and authentication improvements. Optimized connection limits for SMTP/IMAP and fixed the default authentication protocol selection for custom mailboxes — resolving issues for rare providers that support Kerberos authentication.
Adjusted email sync intervals. For mailboxes connected via SMTP/IMAP, the sync interval has been set to 20 minutes while we monitor stability. OAuth-connected mailboxes (Gmail, Outlook) remain at 5 minutes. We plan to reduce the SMTP/IMAP interval back to 10 minutes once stability is confirmed.
Cloud Browser
Fixed black screen when opening Cloud Browser. Some users saw a black screen or the browser failed to start entirely. The root cause was a broken pre-release build of GoLogin's Orbita browser (version 143) that was downloaded in February. The official stable release has since been published, and all broken versions have been removed from our automation servers.
Fixed LinkedIn connection issues via Cloud Browser. New LinkedIn profile connections were failing on one automation server. This has been resolved.
Chrome Extension
Fixed contact saving failures (v2.4.18 → v2.4.20). LinkedIn changed the profile format for some users, which broke contact name parsing in the GetSales extension. Two successive fixes were shipped:
v2.4.18 — resolved the initial name-parsing issue
v2.4.20 — addressed an additional format variation discovered in further testing
Both updates are available after Chrome auto-updates the extension.
Imports
Fixed Basic Search import failures. Contact imports via Basic Search were failing for some LinkedIn profiles due to format changes on LinkedIn's side. Two rounds of fixes were applied to handle all affected profile variations. If you previously saw failed or incomplete Basic Search imports, they should now work correctly.
Whitelabel
Custom links in the bottom-left menu. Whitelabel customers can now add their own links to the bottom-left navigation menu — including API Docs, University, Help Center, Chrome Extension, and MCP Server URLs. This makes it easier to direct your end users to your own resources.