Parent umbrella issue: #495
Source audit: Weekly tech debt audit: dispatch - 2026-07-01
Source audit date: 2026-07-01
Original recommendation
Sync lock stale threshold (30 min) may be too short for large repos
Evidence: src/lib/sync-lock.ts line 23 — MAX_AGE_MS = 30 * 60 * 1000 (30 minutes). For repos with thousands of issues across multiple pages, a sync run could take longer than 30 minutes, causing a second concurrent sync to acquire the lock and both syncs to run simultaneously. This is a deployment-specific concern but worth documenting.
Matched top finding
Evidence: src/lib/sync-lock.ts line 23 — MAX_AGE_MS = 30 * 60 * 1000 (30 minutes). For repos with thousands of issues across multiple pages, a sync run could take longer than 30 minutes, causing a second concurrent sync to acquire the lock and both syncs to run simultaneously. This is a deployment-specific concern but worth documenting.
Parent umbrella issue: #495
Source audit: Weekly tech debt audit: dispatch - 2026-07-01
Source audit date: 2026-07-01
Original recommendation
Sync lock stale threshold (30 min) may be too short for large repos
Evidence:
src/lib/sync-lock.tsline 23 —MAX_AGE_MS = 30 * 60 * 1000(30 minutes). For repos with thousands of issues across multiple pages, a sync run could take longer than 30 minutes, causing a second concurrent sync to acquire the lock and both syncs to run simultaneously. This is a deployment-specific concern but worth documenting.Matched top finding
Evidence:
src/lib/sync-lock.tsline 23 —MAX_AGE_MS = 30 * 60 * 1000(30 minutes). For repos with thousands of issues across multiple pages, a sync run could take longer than 30 minutes, causing a second concurrent sync to acquire the lock and both syncs to run simultaneously. This is a deployment-specific concern but worth documenting.