Preserve active processing locks during seeding
When the migration runs while an indexing-v3 agent is actively processing a document, a row with indexing_v3_agent_status = 'processing' and a recent locked_at misses the stale-processing branch and falls through to pending. Because the claim RPC treats any non-processing job as immediately claimable, the same document can be picked up by another worker during the rollout, duplicating work and burning attempts despite the existing lock.
Useful? React with 👍 / 👎.
Originally posted by @chatgpt-codex-connector[bot] in #134 (comment)
When the migration runs while an indexing-v3 agent is actively processing a document, a row with
indexing_v3_agent_status = 'processing'and a recentlocked_atmisses the stale-processing branch and falls through topending. Because the claim RPC treats any non-processingjob as immediately claimable, the same document can be picked up by another worker during the rollout, duplicating work and burning attempts despite the existing lock.Useful? React with 👍 / 👎.
Originally posted by @chatgpt-codex-connector[bot] in #134 (comment)