fix(kb): report a paused connector as paused, not superseded

Pausing a queued connector releases its token, so testing ownership before
status reported every pause-while-queued — the common case — as a superseded
dispatch. The mismatch is the symptom there; the status is the reason.

Author: waleedlatif1

apps/sim/lib/knowledge/connectors/sync-engine.ts

@@ -1621,11 +1621,13 @@ export async function executeSync(
       .where(eq(knowledgeConnector.id, connectorId))
       .limit(1)
 
-    if (options.dispatchToken && current?.syncLockToken !== options.dispatchToken) {
-      logger.info('Sync superseded by a newer dispatch, skipping', { connectorId })
-      return { ...result, error: 'dispatch_superseded' }
-    }
-
+    /**
+     * Status is checked before ownership because pausing a queued connector
+     * releases its token, so a mismatch is the *symptom* there and the status is
+     * the actual reason. Testing ownership first would report every
+     * pause-while-queued — the common case — as a superseded dispatch, losing
+     * the distinction this branch exists to draw.
+     */
     if (current?.status === 'paused' || current?.status === 'disabled') {
       logger.info('Connector is not accepting syncs, skipping', {
         connectorId,
@@ -1634,6 +1636,11 @@ export async function executeSync(
       return { ...result, error: 'connector_not_syncable' }
     }
 
+    if (options.dispatchToken && current?.syncLockToken !== options.dispatchToken) {
+      logger.info('Sync superseded by a newer dispatch, skipping', { connectorId })
+      return { ...result, error: 'dispatch_superseded' }
+    }
+
     logger.info('Sync already in progress, skipping', { connectorId })
     // Reported as an error so the task wrapper's `success: !result.error` does not
     // present a skipped run as a successful zero-document sync.