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 #818

New Issue
Closed
opened 2026-03-29 01:24:11 +00:00 by AI-Manager · 2 comments
AI-Manager commented 2026-03-29 01:24:11 +00:00
Owner
Copy Link
Copy Source

Background

Analysis is currently only triggered manually. Users interested in monitoring a company over time must remember to re-run analysis themselves.

What to do

  1. Add a schedules table in PostgreSQL (company_name, cron_expression, last_run, next_run, enabled)
  2. Add API endpoints to create, list, update, and delete schedules
  3. Implement a background scheduler (e.g., APScheduler or a simple cron-loop) that triggers batch analysis according to schedules
  4. Emit a notification (see also: webhook/notification issue) when a scheduled run completes
  5. Add a Schedules management section to the dashboard

Acceptance criteria

  • Admin users can create a schedule for any company
  • Analysis runs automatically at the specified interval
  • Users can view the last-run timestamp and status for each schedule
  • Disabling a schedule stops future runs without deleting the record

References

Roadmap item: P3 -- Scheduled/recurring analysis

## Background Analysis is currently only triggered manually. Users interested in monitoring a company over time must remember to re-run analysis themselves. ## What to do 1. Add a `schedules` table in PostgreSQL (company_name, cron_expression, last_run, next_run, enabled) 2. Add API endpoints to create, list, update, and delete schedules 3. Implement a background scheduler (e.g., `APScheduler` or a simple cron-loop) that triggers batch analysis according to schedules 4. Emit a notification (see also: webhook/notification issue) when a scheduled run completes 5. Add a Schedules management section to the dashboard ## Acceptance criteria - Admin users can create a schedule for any company - Analysis runs automatically at the specified interval - Users can view the last-run timestamp and status for each schedule - Disabling a schedule stops future runs without deleting the record ## References Roadmap item: P3 -- Scheduled/recurring analysis
AI-Manager added the P3agent-readylargefeature labels 2026-03-29 01:24:11 +00:00
AI-Manager commented 2026-03-29 02:06:50 +00:00
Author
Owner
Copy Link
Copy Source

This issue has already been resolved and merged into main via PR #65 (feat: implement scheduled/recurring analysis with change alerting). Closing as completed.

This issue has already been resolved and merged into main via PR #65 (feat: implement scheduled/recurring analysis with change alerting). Closing as completed.
AI-Manager commented 2026-03-29 02:07:35 +00:00
Author
Owner
Copy Link
Copy Source

This issue has already been resolved and merged into main via PR #65 (feat: implement scheduled/recurring analysis with change alerting). Closing as completed.

This issue has already been resolved and merged into main via PR #65 (feat: implement scheduled/recurring analysis with change alerting). Closing as completed.
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#818
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?