Troubleshooting

Start by identifying the product, activity, and step that failed. Record the visible error and time before changing the setup. For a payment or transaction, establish what happened to the original operation before trying again. Keep private keys, recovery phrases, session credentials, and stream keys out of screenshots and messages.

​

Account and Wallet Connections

If the chosen activity uses an account or wallet, confirm that you are using the intended product, account, and network. Check whether the required extension or wallet application is available and whether a connection or signing request is waiting. Read the request before approving it; a request for a recovery phrase or private key is not a normal sign-in step. If the page times out, check the connection and the product’s supported browser or wallet instructions. Save any error details before reconnecting. Avoid clearing stored sessions or wallet history as a first step. If you suspect a browser conflict, compare behaviour in another supported browser or a separate test profile while preserving the original session. Do not turn off security protections indiscriminately.

​

Payments and Transaction Errors

A timeout in the interface does not establish that a payment failed.

• Retain the operation reference and any transaction signature.
• Compare the application’s status with the relevant network or provider record.
• Check the intended recipient, asset, network, amount, and the fees shown for that operation.
• Distinguish an unsigned request, a submitted transaction, a confirmed result, and an operation awaiting recovery.
• Follow the selected integration’s recovery guidance before resubmitting or authorising another payment.

Use the fee estimate and funding requirements for that operation and network when checking whether the transaction can proceed. SW4P explains the settlement lifecycle. @sw4p/kit describes operation-state handling for integrations.

​

Games, Scores, and Leaderboards

​

A game will not load

Confirm that the game is offered in the experience you are using and check its browser and device requirements. Record any error and whether the problem affects one game or several. Check that the required page content can load. If an extension or browser setting appears involved, test a scoped change or supported alternative without discarding your existing session or disabling protections broadly.

​

A score is missing

Record the game, session, result, and submission time. Check whether the game reports the run as complete and whether a score submission was acknowledged. Compare the game’s scoring rules, account or participant reference, leaderboard category, and reporting period. If the experience separates test and other environments, confirm which one the result belongs to. Avoid replaying a completed action simply to force a submission. Preserve the record so support can distinguish a missing request, a rejected result, and a display delay.

​

A leaderboard looks delayed

Check the selected game, category, period, and any displayed update time. Refresh the display only after retaining the result you are trying to trace. There is no single update interval for every game or leaderboard. Use that experience’s scoring and support information.

​

Streams and Media Output

​

A destination will not connect

Use the destination’s current ingest instructions and the credentials issued for that destination. Check the server, stream key, required account state, and any whitespace introduced while copying. Test one destination to isolate the problem, then check the intended combined output. Keep stream keys private. Do not replace the endpoint with an old example URL from another setup.

​

Video or audio is missing or unstable

Check the selected sources and device permissions. Confirm that another application is not preventing access to the needed camera or microphone. Compare the preview, a local recording where available, and the destination output to identify where the problem starts. Use supported output settings and distinguish encoding strain from connection-related dropped frames. OBS users can consult its Quick Start Guide for a local setup test and Stream Connection Troubleshooting for dropped frames and disconnections.

​

Destinations behave differently

Compare each destination’s status and requirements independently. One working destination does not confirm the others received the same output. Check whether encoding and distribution happen on the device, through another service, or in a combined setup before estimating required capacity. Keep the known-working configuration while isolating the failed connection. For overlay problems, use OBS Integration or the CTRL Panel Guide.

​

Reward and Claim Questions

SW4P Earn extends SW4P’s economic model into source-aware allocation, claims, rewards, payout schedules, reserves, and reconciliation. Current status: SW4P Earn is not yet publicly available. No staking, liquidity, reward, or claim programme is currently open. There is no public claim schedule or claim action to follow from this guide. A future programme would publish its eligible activity, funding, recipients, allocation rules, claim timing, supported network and addresses, effective date, and support path. If you have a record of a past payment or activity, retain its programme and operation references. A score, point balance, allocation, claim, and confirmed payment have different meanings. Read SW4P Earn for the model and current status.

​

Ask for Help

Provide the product or page, the action attempted, the time, the visible error, the relevant device/browser version, and a short sequence that reproduces the issue. Include an operation or transaction reference where relevant. Redact secrets, private links, personal information, and unrelated account details. Keep an original record privately rather than deleting evidence while troubleshooting. Use the Support Center for the appropriate contact path.