From 186b428b677447078b22cb8aa445737ab996bf4c Mon Sep 17 00:00:00 2001
From: tiennm99 <tiennm99@outlook.com>
Date: Sat, 9 May 2026 13:14:46 +0700
Subject: [PATCH] fix(cron): use empty crons=[] to actually clear CF dashboard
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Commenting out [triggers] left stale schedules visible in the CF
dashboard — Wrangler only pushes declared config, never removes
implicitly. An empty array is the explicit "clear schedules" signal.

Sample schedule preserved as a comment above the empty array so
re-enabling is a single-line edit.
---
 wrangler.toml | 16 +++++++++++-----
 1 file changed, 11 insertions(+), 5 deletions(-)

diff --git a/wrangler.toml b/wrangler.toml
index 55422bf..684909b 100644
--- a/wrangler.toml
+++ b/wrangler.toml
@@ -14,12 +14,18 @@ TZ = "Asia/Ho_Chi_Minh"
 #
 # DISABLED: this worker is parked. I migrated this routine to cron-job.org
 # to keep my CF cron-trigger quota free for other workers (see README).
-# To re-enable, uncomment the block below and `npx wrangler deploy`.
 #
-# [triggers]
-# crons = [
-#   "0 0-17,22-23 * * *", # UTC+7: 00:00 + 05:00..23:00 hourly
-# ]
+# `crons = []` (empty array) is REQUIRED to clear schedules from CF — just
+# omitting/commenting the block leaves stale entries in the dashboard,
+# because Wrangler only pushes what you declare.
+#
+# To re-enable: replace the empty array with your schedule (sample below)
+# and `npx wrangler deploy`.
+#   crons = [
+#     "0 0-17,22-23 * * *", # UTC+7: 00:00 + 05:00..23:00 hourly
+#   ]
+[triggers]
+crons = []
 
 # Workers Logs / traces. `head_sampling_rate = 1` keeps 100% of invocations
 # (low volume here — ~20/day — so full retention is free). Drop to e.g. 0.1