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

Implement scheduled/recurring analysis with change alerting #421

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

Summary

Users cannot set up periodic re-analysis of tracked companies. Automatic alerting on significant changes would enable proactive monitoring.

What to do

  1. Add a scheduled_jobs table with fields: company_name, cron_expression, last_run, next_run, enabled
  2. Use APScheduler (or a Celery beat equivalent) to trigger re-analysis on schedule
  3. After each run, compare the new innovation score with the previous one; if it changes beyond a configurable threshold, record an alert
  4. Expose CRUD endpoints for managing schedules: POST /schedules, GET /schedules, DELETE /schedules/{id}
  5. Display upcoming and past scheduled jobs in the frontend

Acceptance Criteria

  • Creating a schedule causes re-analysis to run at the configured interval
  • An alert is recorded when the innovation score changes by more than the threshold
  • Schedules persist across API restarts
  • Frontend shows the list of active schedules

Reference

Roadmap: P3 - Scheduled/recurring analysis

## Summary Users cannot set up periodic re-analysis of tracked companies. Automatic alerting on significant changes would enable proactive monitoring. ## What to do 1. Add a `scheduled_jobs` table with fields: `company_name`, `cron_expression`, `last_run`, `next_run`, `enabled` 2. Use APScheduler (or a Celery beat equivalent) to trigger re-analysis on schedule 3. After each run, compare the new innovation score with the previous one; if it changes beyond a configurable threshold, record an alert 4. Expose CRUD endpoints for managing schedules: `POST /schedules`, `GET /schedules`, `DELETE /schedules/{id}` 5. Display upcoming and past scheduled jobs in the frontend ## Acceptance Criteria - Creating a schedule causes re-analysis to run at the configured interval - An alert is recorded when the innovation score changes by more than the threshold - Schedules persist across API restarts - Frontend shows the list of active schedules ## Reference Roadmap: P3 - Scheduled/recurring analysis
AI-Manager added the P3agent-readylarge labels 2026-03-27 18:25:32 +00:00
AI-Manager commented 2026-03-27 19:06:49 +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 P3 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#421
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?