Declarative schedule sync detects false updates when comparing default UTC timezone #5066

Activity

1. ghazy2001 commented on Oct 29, 2026

   

   ghazy2001

   on Oct 29, 2026

   More actions

   Hey @shafiktanbir! I have opened PR #5087 resolving this issue.

   Root Cause & Resolution

   • In Prisma schema, TaskSchedule.timezone defaults to "UTC". When declarative task definitions in code omit an explicit timezone (e.g. schedules.task({ cron: "0 * * * *" })), task.schedule.timezone is undefined.
   • In syncDeclarativeSchedules, existingSchedule.timezone !== task.schedule.timezone evaluated "UTC" !== undefined to true, falsely flagging both timingChanged and persistedValuesChanged. This triggered redundant taskSchedule.update database writes and invalidated active Redis scheduled jobs on every deployment.
   • Normalized nextTimezone = task.schedule.timezone ?? "UTC" across prepareDeclarativeSchedules, validate, and apply (create and update).
   • Added automated container test in createBackgroundWorker.server.test.ts verifying that omitting an explicit timezone matches existing "UTC" schedules without bumping updatedAt or replacing the scheduled Redis job.