RaceSlot
Loading the page
RaceSlot is run by one operator, and support is a conversation with them. There is no ticket system and no chat; write an email.
If the contact above says it is not set, ask whoever gave you your invite -- they know who runs this deployment.
Since helper 3.47.0 the server address must start with https://. The sign-in screen refuses anything else with the sentence “The server address must start with https://”, and a saved address that does not is refused in the Activity log on every start. Check the Server field on the helper's sign-in screen, or reinstall from the command on the Downloads page, which carries the right address.
Dry run is ticked by default and lives on the helper's Settings pane. While it is on, the helper claims the work, writes down the click it would have made, and touches nothing; RaceSlot then reports that as a dry run rather than as a registration. Untick it, then press Resume in the rail.
The message names what the helper actually saw. The usual causes are on the PC: the iRacing client is closed, it is sitting at its own sign-in screen, the helper is stopped, or it is still in Dry run. Start the helper before the client -- a client that was already open exposes almost nothing to it -- and try once more. A registration is reported as a success only once the helper has seen iRacing's green “Registered / You may join your session” bar, so a failure is a failure.
RaceSlot only knows about registrations it made itself; nothing can ask iRacing what you are in. If you joined or left a session inside the client, its record has gone stale. One tap of Withdraw resyncs it: if there is genuinely nothing to leave, the helper answers that nothing is registered and the record is cleared.
The Queue tab keeps the reason on the row. “Nothing was attempted -- the PC agent is offline (last seen N ago)” means the PC was off or the helper was not running when the moment came; a queued session waits for the PC and gives up after its window. Other reasons it can give: every write is paused on the server, or the last hour is too close to the ceiling of 20 actions to spend more.
iRacing does not allow a withdrawal in the last 2 minutes before a race starts, so RaceSlot refuses to enter a race, or to switch away from a held one, inside that deadline rather than cost you a forfeit. A race is also refused wherever the operator has not switched race registration on, and the message says which.
A window cannot be drawn over iRacing in exclusive Full Screen mode, and the helper says so rather than drawing invisibly: “The overlay cannot draw over iRacing in Full Screen mode. In iRacing: Options -> Graphics -> Display Mode -> Borderless Window.” VR is not supported at all. Check the hotkey on the helper's Overlay pane too: the default toggles the overlay, and a refused hotkey keeps the previous one.
By default the helper keeps running in the tray when the window is closed or minimised -- the icon beside the clock. Right-click it for Open and Quit; double-click opens the window. The switch is on the helper's Settings pane (“Keep running in the tray when the window is closed”); untick it and the X quits as it used to. The overlay stays up either way.
Include these, and the operator can usually answer from the first email:
To see, correct or delete what RaceSlot holds about you, the privacy policy says what there is and how. Deleting the account is self-service: Setup has a Delete your account control that removes everything at once, after you type your email. Anything you cannot do from a screen, ask [email protected].
If you find a vulnerability in RaceSlot or its helper, tell the operator at [email protected] before anyone else, with enough detail to reproduce it. They will acknowledge it, fix it, and say when it is fixed; please give them the time to.