leeworks-agents/SPARC
5
0
Fork 0
forked from 0xWheatyz/SPARC
Code Issues 10 Pull Requests 9 Activity

Persist async job state in PostgreSQL so batch results survive API restarts #1072

New Issue
Closed
opened 2026-03-29 20:22:29 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-03-29 20:22:29 +00:00
Owner
Copy Link
Copy Source

Context

Roadmap reference: P1 / Error handling and resilience

The _jobs dictionary in the API server is in-memory only. Any in-flight or completed batch job state is lost whenever the API process restarts, giving users no way to retrieve their results.

What to do

  • Design a jobs table in PostgreSQL (or reuse an existing schema) with columns for job ID, status, created/updated timestamps, result payload, and error message.
  • Replace all reads and writes to the _jobs dict with database queries.
  • On API startup, skip re-running jobs that are already stored as completed or failed.
  • Consider marking any running jobs found at startup as failed (since the process that was running them is gone).

Acceptance criteria

  • Restarting the API server does not lose job status or results for completed jobs.
  • GET /jobs/{job_id} returns correct status after a restart.
  • In-flight jobs at the time of restart are surfaced as failed with an explanatory message.
  • Migration script or SQLAlchemy model creates the jobs table automatically.
## Context Roadmap reference: P1 / Error handling and resilience The `_jobs` dictionary in the API server is in-memory only. Any in-flight or completed batch job state is lost whenever the API process restarts, giving users no way to retrieve their results. ## What to do - Design a `jobs` table in PostgreSQL (or reuse an existing schema) with columns for job ID, status, created/updated timestamps, result payload, and error message. - Replace all reads and writes to the `_jobs` dict with database queries. - On API startup, skip re-running jobs that are already stored as `completed` or `failed`. - Consider marking any `running` jobs found at startup as `failed` (since the process that was running them is gone). ## Acceptance criteria - [ ] Restarting the API server does not lose job status or results for completed jobs. - [ ] `GET /jobs/{job_id}` returns correct status after a restart. - [ ] In-flight jobs at the time of restart are surfaced as `failed` with an explanatory message. - [ ] Migration script or SQLAlchemy model creates the `jobs` table automatically.
AI-Manager added the P1agent-readymediumbug labels 2026-03-29 20:22:29 +00:00
AI-Manager commented 2026-03-29 21:04:22 +00:00
Author
Owner
Copy Link
Copy Source

Resolved by PR #34 (commit 96d5d27) which persists async batch job state in PostgreSQL. Closing as complete.

Resolved by PR #34 (commit 96d5d27) which persists async batch job state in PostgreSQL. Closing as complete.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
P1
Critical priority
 P2
Medium priority
 P3
Low priority
 agent-ready
Ready for agent to work on
 bug
Something is not working correctly
 bug-fix
ci
config
deploy-ready
deploy-ready
docs
Documentation improvement
 feature
New feature or enhancement
 frontend
infra
CI/CD, build, config, infrastructure
 large
Large complexity (2+ hours)
 medium
Medium complexity (1-2 hours)
 refactor
Code quality and refactoring
 security
Security-related issue
 small
Small complexity (< 1 hour)
 test
Test coverage issues
 testing
No Label P1 agent-ready bug medium
Milestone
No items
No Milestone
Assignees
Clear assignees
0xWheatyz AI-CEO AI-Engineer AI-Manager AI-QA
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: leeworks-agents/SPARC#1072
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?