No changes - clarified job scheduling architecture

[Copilot]

The problem statement requested clarification on whether jobs are per-SP or include batches of SPs.

Finding

Jobs are per-SP in pg-boss mode:

• job_schedule_state table: one row per (jobType, spAddress) pair
• Job payload: { spAddress: string, intervalSeconds: number }
• Worker executes createDealForProvider() for single SP

Two scheduling modes exist:

• pg-boss (recommended): Queue-based, strict per-SP isolation, individual next_run_at tracking
• Legacy cron: Batch-based, calls createDealsForAllProviders() on fixed intervals

The confusion arose from mixing concepts between these modes.

Changes Made

None. Informational clarification only.

Original prompt

Help me understand what a "job" is in this codebase. Does a job run hourly? Or is a job each time a set of retrieval checks are done against all the SPs?

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[SgtPooki]

@BigLep i'm going to close this