No drivers on server roster — log in via the driver app so name/league register.
Timing reaches this server, but track-limit POSTs come from the driver bridge queue. In the bridge console, look for [cmd-queue] delivered cmdId=tl_… upstream=200. If you only see retries or http=422, restart the bridge after redeploying the server, then trigger a new cut (old game-side 202 responses do not guarantee server delivery).
Incidents 0 · raw violations 0 · https://server--race-control-server--zsf68hxf6ycg.code.run/v1/sessions/…/incidents?category=trackLimits
| Time | Driver | League | Severity | Status | Detail | Actions |
|---|---|---|---|---|---|---|
| No track limits incidents for this session. Confirm API https://server--race-control-server--zsf68hxf6ycg.code.run matches your server, restart the server after updates, then trigger a new violation. | ||||||