Troubleshooting
If something's not working on race day or during plan setup, work down the list below before reaching out.
I'm not getting Discord DMs
The bot DMs you at T-30 / T-15 / T-5 before each stint. If they're not arriving:
- Did you link your Discord? Go to Settings → Discord and check for the green "✅ Linked" panel. If you see "Generate code" instead, you haven't linked yet — see Stay alert (Discord DMs) in the Driver Guide.
- Are your DMs open? Discord respects per-user DM privacy. If your DM settings block messages from server members, the bot can't reach you. Open Discord → User Settings → Privacy & Safety → Allow direct messages from server members.
- Is the bot in the server? Your team's connected Discord server needs the StintIQ bot as a member. Ask your team admin or server admin to verify it's in the member list. See Discord setup (server admin).
- Did your team admin connect the right server? On the team detail page, the "Discord: {server name}" badge shows which server is connected. If that's the wrong server, ask the team admin to reconnect.
A share link returns 404
Share links look like stintiq.app/r/abc123.... If clicking returns "Plan not found":
- The link was rotated. Your team admin generated a fresh URL; the old one is dead immediately. Ask for the current link.
- The plan was deleted. The link stops working when the plan is deleted.
The race countdown is wrong
The race-day countdown reads from race_start_utc and converts to your browser's timezone. If it's wrong:
- Your team admin entered the wrong start time. Compare the time shown on the page with the time you expect. If they disagree, they entered the wrong time.
- Your browser timezone is off. Browsers detect timezone automatically. If your laptop's timezone is wrong, the countdown reads wrong.
A validation warning won't clear
Orange warnings on the plan detail page mean a stint or driver breaks the plan's fair share rule (a driver short of their share, a stint over your ACC server's max, and so on).
- Give a driver more laps if they're short of their share, or move laps off a driver who's over a limit. The stint builder has drag-to-reorder.
- Re-assign a stint if a driver shouldn't be on a particular slot.
- Check the Fair Share Rule on the plan page: it should be the rule for this race's sim, or None if the race doesn't enforce one (an iRacing hosted session, a public ACC server).
If the warning persists after edits, hard-refresh the page (Ctrl-F5 / Cmd-Shift-R).
My Hypercar/GT3 projection looks wrong
Most common cause: wrong NRG inputs. See NRG and car class — Hypercar uses an implicit 100% budget; GT3 needs a BoP lap budget. Mixing them up produces nonsense numbers.
If the projection still looks off after verifying NRG, double-check avg_lap_seconds (sometimes captains type minutes by accident — a 1:45 lap is 105 seconds, not 1.45).
My color or skill rating won't save
The PATCH endpoint silently fails if the API can't reach the database. Hard-refresh the page, retry. If it persists, open the browser console and check for 5xx errors on the PATCH /teams/{id}/members/{user_id} request.
The StintIQ Telemetry Agent
When the agent needs you, its tray icon turns amber. Click it to open the window: the first line says what's wrong, and the fix is under it.
"Can't reach StintIQ"
The agent has had no answer from StintIQ for over 10 minutes. Check the PC's internet connection; the agent keeps trying by itself. Anything it records meanwhile is saved on the PC ("Saved on this PC: 12 updates send when StintIQ is back.") and sent once it's back, up to 24 hours after the race.
"This PC isn't connected to your StintIQ account any more"
The PC was removed on the website, disconnected, unused for 90 days, or the account was deleted. Click Connect this PC in the agent and press Connect on the page that opens. See Install the StintIQ Telemetry Agent.
"iRacing isn't sharing its live data"
iRacing is running, but its telemetry option is off. Close iRacing, open Documents\iRacing\app.ini, find the line irsdkEnableMem and make sure it says irsdkEnableMem=1, then start iRacing again.
"Le Mans Ultimate isn't answering"
Le Mans Ultimate is running, but isn't answering the agent yet. Wait until it reaches its main menu. If the message stays, restart Le Mans Ultimate.
"Which race is this?"
Two of your StintIQ races could be this session (two teams racing the same evening, say). Open the agent and pick the race, or None of these. Until you answer, it saves what it sees on your PC; it sends that once you pick, and deletes it if you choose None of these.
The tray stays blue in our race
Blue means a session the agent can see, but not one of your team's races. Check that the plan's race is in the session's sim (the team's sim), that the plan's schedule covers now (server open to race end), and that the session is online, not offline testing. If the race really isn't being matched, a captain can check the plan's Schedule and Track.
My stints show "Unlinked driver"
You haven't linked your sim identity for that sim, or you removed it. Link it under Settings → StintIQ Telemetry Agent → Your sim identities (see Link your sim identity). Stints recorded before you linked stay "Unlinked driver"; new ones are named. "No driver seen" is different: nobody was in the car yet, usually the first seconds after the green.
Who's ready says "No agent" or "Not running"
That driver hasn't installed the agent, or it isn't running on their PC. Send them Install the StintIQ Telemetry Agent. With Start with Windows on, the agent starts by itself.
"No new data from the car for 2 min"
No agent in the session has sent anything for that long. Everyone's agent may have dropped out, the session may have ended, or the agents may be paused. Check Who's ready: a PC that lost its connection sends what it saved once it's back.
"Fuel: Sam's StintIQ Telemetry Agent isn't connected"
In iRacing only the driving PC sees the fuel. Ask the driver to start their agent (or un-pause it); fuel comes back on the next lap.
Still stuck
Join the StintIQ Discord. The team and community are responsive — most issues get a fix or workaround within an hour.
Have questions? Join our Discord →