If StakeClaimer is installed but no claims are appearing, first identify where the process stops: the relay detects a code, your device receives it, and Stake accepts or rejects the claim. These are separate events. This guide covers checks after installation; use the installation guide if the claimer panel has never appeared.
The panel is missing
Check that the userscript manager and StakeClaimer script are enabled on the site you have open. Revisit the browser-specific permission steps on the installation page, then reload the Stake tab. On Android, use the app setup instructions instead of desktop extension instructions.
The panel reports no connection or no subscription
Confirm that the device has an internet connection, the Stake session is signed in and the subscription belongs to the account you are using. Read the status message before changing filters. A page left open on a sleeping computer cannot process new events; a visible browser tab can also have been suspended.
If your plan is active but the status disagrees, check the subscription bot's status response or ask support to check the account association. Reinstalling repeatedly or purchasing another subscription does not identify the underlying problem.
The public feed has a code, but history has no matching result
Compare the platform and timestamp in the live feed with the account and device you are inspecting. COM and US are different destinations. The public page records detections and refreshes periodically; it does not report whether your account received or claimed an entry.
Look at whether the device was connected at that time. If the issue is intermittent, record one example with the time, platform and visible status. That is more useful for diagnosis than changing several settings and losing the original conditions.
History shows a skipped or rejected claim
- Skipped: check your selected code values or strategy settings. A filter may intentionally exclude an entry.
- Already claimed: inspect earlier history before treating the result as a new failure.
- Eligibility or limit message: compare it with the original promotion and the account's own status. The relay cannot grant eligibility.
- Expired or unavailable: faster delivery cannot restore an offer whose allocation has ended.
Use the exact message shown; do not assume every unsuccessful claim has the same cause. The claim-limit guide explains why a promotion cap, account limit and local filter need different responses.
Send a useful support report
Include your device/browser, the affected platform, the approximate UTC time, the visible error and the relevant history entry. Redact passwords, session keys and other login credentials before sharing a screenshot. The contact page provides the support options.