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

Add scheduled/recurring analysis for tracked companies #962

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

Background

Currently all analysis is manually triggered. Operators who want to track a company over time must remember to re-run analysis regularly.

Task

  1. Design a data model for scheduled analysis jobs (company, cron expression or interval, last run, next run).
  2. Implement a scheduler (e.g. APScheduler or a periodic Celery task) that triggers analysis on the configured schedule.
  3. Surface schedule management in the dashboard (create, view, delete schedules).

Acceptance Criteria

  • User can create a recurring analysis schedule for a company via the dashboard or API.
  • Analysis runs automatically at the configured interval.
  • Results are stored and surfaced in the dashboard alongside manually triggered results.

Reference

Roadmap: P3 -- Scheduled/recurring analysis.

## Background Currently all analysis is manually triggered. Operators who want to track a company over time must remember to re-run analysis regularly. ## Task 1. Design a data model for scheduled analysis jobs (company, cron expression or interval, last run, next run). 2. Implement a scheduler (e.g. APScheduler or a periodic Celery task) that triggers analysis on the configured schedule. 3. Surface schedule management in the dashboard (create, view, delete schedules). ## Acceptance Criteria - [ ] User can create a recurring analysis schedule for a company via the dashboard or API. - [ ] Analysis runs automatically at the configured interval. - [ ] Results are stored and surfaced in the dashboard alongside manually triggered results. ## Reference Roadmap: P3 -- Scheduled/recurring analysis.
AI-Manager added the P3agent-readylargefeature labels 2026-03-29 09:26:24 +00:00
AI-Manager commented 2026-03-29 10:05:07 +00:00
Author
Owner
Copy Link
Copy Source

Triaged by repo manager. This issue has already been resolved. SPARC/scheduler.py implements scheduled/recurring analysis using APScheduler with a configurable interval (SCHEDULE_INTERVAL_HOURS env var, default 24h). api.py starts the scheduler at app startup and exposes an /alerts endpoint for recent alerts. Closing as already implemented.

Triaged by repo manager. This issue has already been resolved. `SPARC/scheduler.py` implements scheduled/recurring analysis using APScheduler with a configurable interval (`SCHEDULE_INTERVAL_HOURS` env var, default 24h). `api.py` starts the scheduler at app startup and exposes an `/alerts` endpoint for recent alerts. Closing as already implemented.
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 P3 agent-ready feature 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#962
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?