hermes - 💡(How to fix) Fix [BUG] Scheduler prematurely marks repeating cron jobs as 'completed' after first successful run [1 pull requests]

Description

A bug has been identified in the cron scheduler where jobs configured with a repeat count (e.g., repeat: 3 times) are being incorrectly transitioned to a completed state after the very first successful execution. This prevents subsequent scheduled runs from triggering.

Steps to Reproduce

1. Create a cron job with a repeat count greater than 1 (e.g., repeat: 3 times) and a duration (e.g., schedule: 2m).
2. Wait for the first execution to complete successfully.
3. Inspect the job status.

Observed Behavior

The job status is marked as state: completed and repeat: 1/3 immediately after the first run. The scheduler stops processing the job, and the remaining scheduled runs do not occur.

Expected Behavior

The job should remain in an active state, and the repeat counter should increment (e.g., 2/3, 3/3) until all requested iterations have been performed.

Technical Analysis (RCA)

Internal inspection of state.db suggests the state machine transition logic in the scheduler is incorrectly treating the completion of a single task instance as the completion of the entire job lifecycle for repeating tasks.