Bug Fix

KW Command connections no longer sit on Sync Queued forever

What We Fixed

Connecting KW Command (and other Rollout CRMs) could get stuck on “Sync Queued, waiting for Rollout to finish its initial database sync” even after authentication succeeded. That happened when a second teammate reused a Rollout credential that had already finished its one-shot database sync — disconnecting and reconnecting did not clear it.

The new connection now inherits the teammate’s ready-signal so the import can start, a missed callback is recovered automatically, and the panel shows a Retry Sync action instead of spinning forever.

Thank you to everyone who reported this.