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

New issue

Closed

opened 2026-05-25 05:34:41 -04:00 by zgaetano · 1 comment

zgaetano commented

2026-05-25 05:34:41 -04:00

Owner

Fixed in migration 016-fix-job-type-enum.sql — added expires_at column to jobs with 24h TTL on trim rows, and added the missing enum values so the inserted job_type matches reality. See #75 / #90.

Fixed in migration `016-fix-job-type-enum.sql` — added `expires_at` column to `jobs` with 24h TTL on trim rows, and added the missing enum values so the inserted job_type matches reality. See #75 / #90.

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:41:14 -04:00

Author

Owner

Fix Plan — #70 batch-trim creates jobs row with wrong job_type

Root cause: batch-trim creates a jobs row with type 'trim' and status 'queued'. The in-database jobs row for trim jobs has no associated BullMQ job ID visible in /jobs. If trim job fails, the jobs row stays 'queued' forever.

Fix: Either make jobs.js also query the DB jobs table (UNION with BullMQ state), or remove the INSERT in batch-trim entirely and track status purely via temp_segments.

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

## Fix Plan — #70 batch-trim creates jobs row with wrong job_type **Root cause:** batch-trim creates a jobs row with type 'trim' and status 'queued'. The in-database jobs row for trim jobs has no associated BullMQ job ID visible in /jobs. If trim job fails, the jobs row stays 'queued' forever. **Fix:** Either make jobs.js also query the DB jobs table (UNION with BullMQ state), or remove the INSERT in batch-trim entirely and track status purely via temp_segments. **Files:** src/routes/assets.js (batch-trim), src/routes/jobs.js **Effort:** ~1h **Priority: P2 — data consistency

zgaetano closed this issue

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

zgaetano referenced this issue

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

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