Skip to main content

Troubleshooting

secret_unavailable​

Confirm the Secret is named exactly GUARDYN_API_KEY, belongs to the correct game, allows api.guardyn.xyz, and is being tested in a supported published or collaborative environment.

http_0​

The request did not receive an HTTP response. Enable HTTP requests, verify HTTPS connectivity, and check Guardyn status. Restriction checks fail open.

401 invalid_api_key​

The key is incomplete, revoked, or belongs to a different workspace. Create a replacement and update the Roblox Secret.

404 game_not_found​

The supplied Guardyn game ID is disabled, incorrect, or belongs to a different workspace than the API key. Do not use the Roblox universe ID in game_id.

402 subscription_inactive​

New reports stop after the grace period. Existing restrictions continue to answer checks and remain exportable.

429 report_limit_reached​

The workspace has reached its calendar-month allowance. Do not silently discard the player's concern; direct the player to Roblox Report Abuse.

Duplicate cases​

Generate client_report_id once when the player submits, and reuse that exact value for retries. Generating a new ID for each attempt creates separate cases.

Player was not restricted​

Confirm the restriction and join check use the same Guardyn game and the current value of Player.User.Id. Do not use a scoped identifier copied from a different game. Check Roblox output for a fail-open warning.