From 18380822ead1a1bb7552aeebdc740d972579f1e7 Mon Sep 17 00:00:00 2001 From: hugocasa Date: Fri, 28 Aug 2026 17:59:21 +0200 Subject: [PATCH] fix: render both sides of the comparison with the same formatter --- .../triggers/schedules/ScheduleEditorInner.svelte | 6 +++--- frontend/src/routes/(root)/(logged)/schedules/+page.svelte | 7 +++---- 2 files changed, 6 insertions(+), 7 deletions(-) diff --git a/frontend/src/lib/components/triggers/schedules/ScheduleEditorInner.svelte b/frontend/src/lib/components/triggers/schedules/ScheduleEditorInner.svelte index dd02b5b301..6a4d5cd8dc 100644 --- a/frontend/src/lib/components/triggers/schedules/ScheduleEditorInner.svelte +++ b/frontend/src/lib/components/triggers/schedules/ScheduleEditorInner.svelte @@ -35,7 +35,6 @@ emptyString, formatCron, msToReadableTime, - msToReadableTimeShort, sendUserToast, cronV1toV2 } from '$lib/utils' @@ -944,8 +943,9 @@ /> {#if outlastingMs && runsSample?.interval_s} - Recent runs have been taking about {msToReadableTimeShort(outlastingMs, 0)}, against {msToReadableTime( - runsSample.interval_s * 1000 + Recent runs have been taking about {msToReadableTime(outlastingMs, 0)}, against {msToReadableTime( + runsSample.interval_s * 1000, + 0 )} between scheduled events. Script runs never overlap, so the next run is only queued once the previous one has completed: this schedule is running less often than its cron asks for. To keep the cadence, schedule a flow instead, which queues its next run when the diff --git a/frontend/src/routes/(root)/(logged)/schedules/+page.svelte b/frontend/src/routes/(root)/(logged)/schedules/+page.svelte index 06b33ca921..3c3504d66c 100644 --- a/frontend/src/routes/(root)/(logged)/schedules/+page.svelte +++ b/frontend/src/routes/(root)/(logged)/schedules/+page.svelte @@ -11,7 +11,6 @@ displayDate, getLocalSetting, msToReadableTime, - msToReadableTimeShort, storeLocalSetting } from '$lib/utils' import { runsOutlastingInterval } from '$lib/components/schedules/scheduleDrift' @@ -657,9 +656,9 @@ {#snippet text()}
- Runs have been taking about {msToReadableTimeShort(outlastingMs, 0)}, longer - than the {msToReadableTime(interval_s! * 1000)} between scheduled events, so - this schedule is running less often than its cron asks for. + Runs have been taking about {msToReadableTime(outlastingMs, 0)}, longer than + the {msToReadableTime(interval_s! * 1000, 0)} between scheduled events, so this + schedule is running less often than its cron asks for.
{/snippet}