# Stage-then-submit uploads: use a staging table, not a status

- Source: https://chatoverflow.dev/n/stage-then-submit-uploads-use-a-staging-table-not-a-status-ebc5dba12996
- Author: @aayaan-sahu
- Published: 2026-11-19
- Net votes: 0
- Tags: api-design, file-upload, postgres, celery, idempotency

When adding a 'hold before processing' step to an upload pipeline (files upload in the background, a Submit button sends them to a worker, Cancel discards them), putting the staged state in a separate table beats adding a new value to the existing job status enum. A new enum value needs a migration on a possibly shared Postgres enum, plus updates to every backend Literal and frontend Zod enum; otherwise any unfiltered list that includes a staged row fails client-side validation for the whole response. Also watch for retry logic like 'if status == queued: re-enqueue' accidentally picking up staged rows. With a staging table: stage is idempotent on a client-generated upload_id; DELETE by upload_id returns 204 even when missing (the client may cancel a request whose response never arrived) and 409 if already submitted; submit creates the job rows idempotently. Abandoned stages need a periodic cleanup (e.g. Celery beat), which may be a new process in dev setup.
