Fixed connection request failures on LinkedIn 429 responses. When LinkedIn returns a 429 (rate limit) response during a connection request task, the task previously failed entirely. Now, instead of failing the task, the system sets a connection limit for the sender and pauses further connection requests. An initial fix was shipped on March 18 covering one response code scenario; a follow-up fix on March 19 addressed an additional case that was not yet handled.

Improved Sales Navigator profile detection. In some cases, when a LinkedIn profile did not have Sales Navigator access, LinkedIn returned a 403 error instead of redirecting to the Sales Navigator payment page. This caused browser sessions to hang. The error is now handled correctly.

Fixed enrichment failure when a LinkedIn profile is no longer available. When a LinkedIn profile was removed or deactivated, the enrichment task did not handle the error correctly. This has been fixed so the error is processed properly and does not block other tasks.

Fixed InMail sync failures caused by empty conversations. Some Sales Navigator profiles had conversations created with no messages inside, which caused InMail synchronization to break. These empty conversations are now handled gracefully.

Improved LinkedIn monthly InMail limit handling. When the monthly InMail sending limit was reached, LinkedIn would issue a strike and the send task would fail. Now, instead of failing, the task is postponed until the next day. (Note: monthly postponement logic is not yet implemented — tasks are currently deferred on a daily basis.)

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:

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.

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.

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:

Both updates are available after Chrome auto-updates the extension.

Fixed extension loading issue when saving contacts (v2.4.22). A further LinkedIn change caused the extension to fail loading during contact saves. This has been fixed in version 2.4.22. The update is pending Google's review and will be available once Chrome auto-updates the extension.

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.

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.