From 6c7f823569c333ef3714eee2a2c004f0c5693fb2 Mon Sep 17 00:00:00 2001 From: Barry <53959224+cal-gooo@users.noreply.github.com> Date: Thu, 19 Mar 2026 07:39:47 -0400 Subject: [PATCH] fix(test): use everyMs instead of intervalMs in CronSchedule fixture Co-Authored-By: Claude Sonnet 4.6 --- src/cron/service/timer.apply-job-result.test.ts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/cron/service/timer.apply-job-result.test.ts b/src/cron/service/timer.apply-job-result.test.ts index 4c3e02d40d5..2f17e84d35a 100644 --- a/src/cron/service/timer.apply-job-result.test.ts +++ b/src/cron/service/timer.apply-job-result.test.ts @@ -141,7 +141,7 @@ describe("applyJobResult – delivered=true overrides error status (#50170)", () it("does not apply error backoff to nextRunAtMs for recurring job when delivered=true overrides error", () => { // Use a high-frequency schedule so the backoff (30 s minimum) would // exceed the natural interval and push nextRunAtMs out if applied. - const schedule = { kind: "every" as const, intervalMs: 5_000 }; + const schedule = { kind: "every" as const, everyMs: 5_000 }; const jobError = createJob({ schedule }); const jobOk = createJob({ id: "test-job-2", schedule });