StintIQStintIQ
CommunityLogin

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:

  1. 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.
  2. 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.
  3. 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).
  4. 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 violates the ruleset (iRacing fair-share, ACC stint length, 24H Series fair-share, etc.).

  • Reorder stints if a driver is over- or under-allocated. The stint builder has drag-to-reorder.
  • Re-assign a stint if a driver shouldn't be on a particular slot.
  • Change the ruleset to "Generic" if the warning isn't relevant (e.g., a non-iRacing race with iRacing rules applied).

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.

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 →