Register Login

Troubleshooting

Output messages, a Local Secret that is not saved, Team Test and refused requests.

Messages in the Output

Every SDK line starts with [R3FTO]. With quiet = true, only warnings print.

Messages in the Output and what to do
You seeWhat to do
this place is not publishedPublish the game (File, Publish to Roblox). DataStores and R3FTO need its universe ID.
Allow HTTP Requests is offTurn it on: File, Experience Settings, Security.
the secret R3FTO_SDK_TOKEN is not available (Roblox: …)The text after "Roblox:" is Roblox's own message. In Studio, add the Local Secret and check that it was saved: The Local Secret is not saved. On Team Test or a live server, add it in Creator Hub Secrets. Name R3FTO_SDK_TOKEN, domain r3f.to.
server signals are not sent: the SDK token secret is not availableAdd the secret as in the row above. Until then, receipts keep only their DataStore copy.
delivery attempt … failed (not_configured, …)The secret is missing on this server, so nothing was sent. Add the secret. The receipt keeps its DataStore copy.
delivery attempt … failed (ambiguous, …)The request did not complete. The SDK sends it again, and R3FTO never counts it twice. If Allow HTTP Requests is off, turn it on.
DataStore attempt … failedIn Studio, turn on Enable Studio Access to API Services. On a live server, the SDK tries again by itself.
HTTP 401 AUTHENTICATION_REQUIREDThe secret does not hold a valid SDK token. Copy the token again from the Roblox tab and put it in the secret.
HTTP 401 CREDENTIAL_REVOKEDRoblox activity: Revoked token. The token was regenerated. Put the current token in the secret.
HTTP 403 ENVIRONMENT_MISMATCHRoblox activity: Test token in Production or Production token in Test. Use the token that matches ENVIRONMENT in R3FTOStart.
HTTP 403 UNIVERSE_MISMATCHRoblox activity: Wrong universe. Check the universe ID on the Roblox tab of the Platforms page.
HTTP 403 SIMULATION_NOT_ALLOWEDRoblox activity: Simulated receipt in Production. Simulated receipts work only in Test.
R3FTO refused the server signalThe HTTP code in the line matches a row above. Receipts are not affected.
key panel: not availableThe game is not Roblox-ready in Production yet, or it is paused. See Readiness on your game page.
key panel: try again laterR3FTO could not answer. The player can try again in a moment.
R3FTO refused a key panel request (<detail>); check the SDK token and the environmentCheck that the SDK token belongs to this game and this environment.
key panel requests are not sent: the SDK token secret is not available (see the warning at start)Add the SDK token secret as described in Setup.
openKeyPanel: R3FTO.start has not runCall R3FTO.start before opening the panel.
openKeyPanel: not a player in this serverPass a Player who is in this server.
openKeyPanel: the KeyPanelGui folder is missingInstall the full R3FTO model, or add the KeyPanelGui folder as in the Setup layout.
a receipt was not recordedPass the exact table Roblox gave your handler.
server closing with … receipt(s) that have no durable copy yetThose receipts were saved nowhere and are lost. Fix the other warnings. If it says some "never started", check that R3FTOStart runs.
[Example] R3FTO did not start: …The reason follows. R3FTOStart must be a Script in ServerScriptService, and ENVIRONMENT must be "test" or "production".
No [R3FTO] line at allCheck that R3FTOStart is a Script, not a LocalScript, and that R3FTO is under ServerScriptService.

The SDK never writes a token or a PlayerId to the Output. Share Output lines with R3FTO freely.

The Local Secret is not saved

Studio can list the secret and still not save it. Then the Output says, for example, the secret R3FTO_SDK_TOKEN is not available (Roblox: Can't find secret with given key), and after Studio restarts the secret is gone.

  1. Stop Play.
  2. Open File, Experience Settings, Security, and turn on Enable Studio Access to API Services if it is off.
  3. In Local Secrets, create the secret again: Name R3FTO_SDK_TOKEN, Secret: the Test token, Domain r3f.to.
  4. Select Save. It must not be greyed out.
  5. Open Experience Settings again. The secret must still be in the list.
  6. Select Play. The secret warning is gone.

If Studio still does not save it, test with Team Test (below).

Team Test and live servers

Local Secrets work only when you select Play in Studio. Team Test and live servers read the secret from Creator Hub instead: your experience, Secrets, Create Secret, with the name R3FTO_SDK_TOKEN and the domain r3f.to. The token in that secret must match ENVIRONMENT in R3FTOStart. For Team Test with "test", use the Test token. For your live game with "production", use the Production token. Your experience has one Creator Hub secret with this name. When you go live, it must hold the Production token.

In Studio, open the Test tab and select Team Test, then Start.

Refused requests on Roblox activity

When R3FTO refuses a request from your game, Roblox activity shows a Refused request row, one for each reason, request and hour. The request is a Receipt, a Referral or a Server signal. Last SDK signal on the Roblox tab can also show the newest short reason. Open the row to see the reason and what to do. The Output rows above list each reason.

A request without a valid token (HTTP 401 AUTHENTICATION_REQUIRED) cannot be linked to your game, so it is not listed. It shows only in the Output.

Documentation

Back to site