Your code didn't arrive

Requesting a sign-in code always answers that it worked, whether or not an email actually went out. That's deliberate, so a reassuring response by itself isn't proof a code is on its way. Work through the checklist below before assuming something's broken.

Check these first

1. Look in spam or junk. Mail from a sender you haven't emailed before is exactly what a spam filter is tuned to catch.
2. Check the address you typed. A single mistyped character sends the code to a mailbox you don't own, and you'll never see it arrive.
3. Wait a minute before asking again. Requesting a code for the same address twice in a short window doesn't send a second email, even though the form still answers that it worked.
4. Ask again once you've waited. A request outside that window sends a new code and invalidates the previous one, so use the latest one you asked for.

Why "it worked" doesn't mean an email was sent

The sign-in form gives the same success response whether the address has an account, whether a code was already sent to it a moment ago, or whether nothing was sent at all. A different answer for each of those cases would leak information: it would let anyone check whether a stranger's email address has an account on rifts.to, or has a code in flight right now, by watching how the form responds alone. So it gives one answer every time, and the checklist above is what actually tells you what happened.

When it's a real failure

Occasionally the email itself fails to send, and that case isn't hidden behind the same reassuring message. You'll see an explicit error saying the email couldn't be sent, instead of the usual "check your inbox" screen. If you see that, wait a few minutes and try again; it's usually temporary. If it keeps happening, contact support and mention what the error said. This is the one case that's different from everything above: it's rifts.to telling you outright that something went wrong on our end, not something to troubleshoot on yours.

If you were also trying to claim a survey

The screen that follows publishing a survey can offer to email you a link to save it to an account in the same step you sign in. That request goes through the same code, so the checklist above applies to it too: check spam, check the address, and wait out the throttle before assuming nothing was sent. If the code does arrive and you sign in with it, the survey is claimed as part of that same step; you don't need to claim it separately afterward.

Requesting the same code over and over doesn't make it arrive any faster. If the first request didn't go anywhere, sending five more in a row won't either, since they're throttled to the same one email until the window passes. One request, a short wait, and a second request if the first didn't land: that's the whole process.