BUG: Batch-trim DB `jobs` row is orphaned — no status lifecycle, `job_type` enum is stale #90

New issue

Closed

opened 2026-05-25 19:29:05 -04:00 by zgaetano · 1 comment

zgaetano commented

2026-05-25 19:29:05 -04:00

Owner

Fixed via migration 016 — jobs.expires_at TTL ensures batch-trim rows don't sit orphaned, and the trim worker writes completed/failed status correctly now that job_status has the completed enum value. See #75, #70.

Fixed via migration 016 — `jobs.expires_at` TTL ensures batch-trim rows don't sit orphaned, and the trim worker writes `completed`/`failed` status correctly now that `job_status` has the `completed` enum value. See #75, #70.

zgaetano changed title from ~~BUG: Trim jobs invisible in Jobs screen — inserted into DB jobs table but screen reads BullMQ only~~ to BUG: Batch-trim DB jobs row is orphaned — no status lifecycle, job_type enum is stale

2026-05-25 19:29:26 -04:00

~~zgaetano referenced this issue 2026-05-26 01:31:48 -04:00~~

BUG: job_type and job_status enums don't match — jobs.js DB table uses job_type ENUM with missing values #75

zgaetano referenced this issue from a commit

2026-05-26 10:10:49 -04:00

fix: close all 24 open issues (#40–#94)

zgaetano commented

2026-05-26 19:33:19 -04:00

Author

Owner

Fix Plan — #90 Batch-trim DB jobs row orphaned

Root cause: assets.js:batch-trim INSERTs a row into jobs DB table with type "trim" status "queued", but jobs.js GET route reads exclusively from BullMQ queues — never from jobs DB table. The DB row is invisible and permanent.

Fix (choose one):

Option A: Make jobs.js also query the jobs DB table, UNION with BullMQ state. Show combined status.

Option B (simpler): Stop writing to jobs DB table in batch-trim. Track status purely via BullMQ job state + temp_segments table. Remove the dead INSERT.

Also fix: temp_segments.job_id FK → ON DELETE CASCADE needs the actual BullMQ job ID or the DB jobs.id to match what gets inserted.

Files: src/routes/assets.js (batch-trim handler), src/routes/jobs.js
Effort: ~1.5h
**Priority: P2 — data consistency

## Fix Plan — #90 Batch-trim DB jobs row orphaned **Root cause:** `assets.js:batch-trim` INSERTs a row into `jobs` DB table with type `"trim"` status `"queued"`, but `jobs.js` GET route reads exclusively from BullMQ queues — never from `jobs` DB table. The DB row is invisible and permanent. **Fix (choose one):** **Option A:** Make `jobs.js` also query the `jobs` DB table, UNION with BullMQ state. Show combined status. **Option B (simpler):** Stop writing to `jobs` DB table in `batch-trim`. Track status purely via BullMQ job state + `temp_segments` table. Remove the dead INSERT. **Also fix:** `temp_segments.job_id` FK → `ON DELETE CASCADE` needs the actual BullMQ job ID or the DB `jobs.id` to match what gets inserted. **Files:** `src/routes/assets.js` (batch-trim handler), `src/routes/jobs.js` **Effort:** ~1.5h **Priority: P2 — data consistency

zgaetano referenced this issue

2026-05-26 21:58:50 -04:00

BUG: POST /assets/batch-trim creates jobs table row with wrong job_type — no matching pg_enum value #70

zgaetano closed this issue

2026-05-26 21:58:57 -04:00