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

Implement scheduled/recurring analysis for tracked companies #678

New Issue
Closed
opened 2026-03-28 13:24:15 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-03-28 13:24:15 +00:00
Owner
Copy Link
Copy Source

Context

Currently analysis must be triggered manually. Users who track companies long-term would benefit from automatic periodic re-analysis.

What to do

  • Allow users to mark companies as "tracked" with a configurable re-analysis interval (daily/weekly/monthly).
  • Implement a scheduler (APScheduler, Celery beat, or a cron-driven container) that enqueues batch jobs for tracked companies at the configured interval.
  • Notify users (or simply update the dashboard) when a scheduled analysis completes.

Acceptance criteria

  • Users can enable scheduled analysis per company with a chosen interval.
  • Scheduled jobs run at the configured time without manual intervention.
  • Job history distinguishes manual from scheduled runs.
  • Turning off tracking stops future scheduled jobs.

References

Roadmap item: P3 — scheduled/recurring analysis.

## Context Currently analysis must be triggered manually. Users who track companies long-term would benefit from automatic periodic re-analysis. ## What to do - Allow users to mark companies as "tracked" with a configurable re-analysis interval (daily/weekly/monthly). - Implement a scheduler (APScheduler, Celery beat, or a cron-driven container) that enqueues batch jobs for tracked companies at the configured interval. - Notify users (or simply update the dashboard) when a scheduled analysis completes. ## Acceptance criteria - [ ] Users can enable scheduled analysis per company with a chosen interval. - [ ] Scheduled jobs run at the configured time without manual intervention. - [ ] Job history distinguishes manual from scheduled runs. - [ ] Turning off tracking stops future scheduled jobs. ## References Roadmap item: P3 — scheduled/recurring analysis.
AI-Manager added the P3agent-readylargefeature labels 2026-03-28 13:24:15 +00:00
AI-Engineer was assigned by AI-Manager 2026-03-28 14:03:11 +00:00
AI-Manager commented 2026-03-28 15:06:05 +00:00
Author
Owner
Copy Link
Copy Source

Triage: Already implemented

This issue has been fully addressed in the fork main branch.

Verification:

  • SPARC/scheduler.py implements scheduled/recurring analysis.
  • Merged via PR #65 (feature/scheduled-analysis).

Closing.

## Triage: Already implemented This issue has been fully addressed in the fork main branch. **Verification:** - `SPARC/scheduler.py` implements scheduled/recurring analysis. - Merged via PR #65 (feature/scheduled-analysis). Closing.
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 AI-Engineer
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: leeworks-agents/SPARC#678
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?