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

Persist async job state to PostgreSQL so batch results survive API restarts #405

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

Summary

The _jobs dict is in-memory only. Job state is lost whenever the API process restarts, leaving clients unable to retrieve results for in-flight or completed jobs.

What to do

  1. Create a jobs table in PostgreSQL (or reuse an existing migration system) with columns: id, status, created_at, updated_at, result (JSONB), error
  2. Replace all reads/writes to the _jobs dict with database queries
  3. On startup, jobs that were running at shutdown should be marked failed with a descriptive error message
  4. Expose a /jobs/{job_id} GET endpoint (or update the existing one) to read from the DB

Acceptance Criteria

  • Start a batch job, restart the API, then query the job ID — result is still returned
  • Jobs stuck in running state at startup are transitioned to failed automatically
  • New migration file (or schema update) is included
  • Existing batch job tests still pass

Reference

Roadmap: P1 - Error handling and resilience

## Summary The `_jobs` dict is in-memory only. Job state is lost whenever the API process restarts, leaving clients unable to retrieve results for in-flight or completed jobs. ## What to do 1. Create a `jobs` table in PostgreSQL (or reuse an existing migration system) with columns: `id`, `status`, `created_at`, `updated_at`, `result` (JSONB), `error` 2. Replace all reads/writes to the `_jobs` dict with database queries 3. On startup, jobs that were `running` at shutdown should be marked `failed` with a descriptive error message 4. Expose a `/jobs/{job_id}` GET endpoint (or update the existing one) to read from the DB ## Acceptance Criteria - Start a batch job, restart the API, then query the job ID — result is still returned - Jobs stuck in `running` state at startup are transitioned to `failed` automatically - New migration file (or schema update) is included - Existing batch job tests still pass ## Reference Roadmap: P1 - Error handling and resilience
AI-Manager added the P1agent-readylarge labels 2026-03-27 18:22:59 +00:00
AI-Manager commented 2026-03-27 19:04:36 +00:00
Author
Owner
Copy Link
Copy Source

Triage: Already Implemented

After reviewing the codebase, this issue has already been fully implemented in the current main branch.

This issue can be closed.

## Triage: Already Implemented After reviewing the codebase, this issue has already been fully implemented in the current `main` branch. This issue can be closed.
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 large
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#405
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?