Mauricio Siu 4e38925119 fix: pass timezone when removing repeatable schedule job ... removeJob() for type 'schedule' computed the BullMQ repeatable key using only the cron pattern, without the timezone. scheduleJob() always registers the repeatable job with tz set (job.timezone || UTC), so BullMQ's repeat key (name:jobId:endDate:tz:pattern) never matched on removal — removeRepeatable silently no-op'd and the job kept firing forever, surviving disable, delete, and reboots. Forward timezone through removeJob (queue.ts), the /update-backup lookup (index.ts), and the disable/delete call sites in the schedule router.		2026-09-01 01:31:59 -06:00
..
api	feat: upgrade to TypeScript 7 and Next.js 16.3	2026-08-11 01:39:09 -06:00
dokploy	fix: pass timezone when removing repeatable schedule job	2026-09-01 01:31:59 -06:00
monitoring	fix: enhance container metrics query to support wildcard matching for container names	2026-03-08 16:16:45 -06:00
schedules	fix: pass timezone when removing repeatable schedule job	2026-09-01 01:31:59 -06:00