Stop adding actions to the incident
Once a round appears frozen, stop tapping controls. Further inputs can create a more complicated sequence and make it harder to identify the original point of interruption. Do not deposit, increase a stake or start another round as a diagnostic test.
Note whether the display is entirely still, whether background effects continue and whether a status message is visible. These details describe the symptom without assuming that movement proves a healthy connection or stillness proves a rejected action.
Record time with a time zone
Write the approximate local time and time zone. If the device clock may be wrong, say so. An honest approximation is more useful than a precise-looking timestamp reconstructed from uncertain memory.
Add the game name exactly as displayed and any visible round identifier. If no identifier is visible, do not invent one or expose account details while searching. Available recorded history may supply the relevant entry later.
Use a compact incident card
The following fields keep the report focused. Fill them with observations and leave unknown details clearly marked as unknown.
- Before the freeze
- The last deliberate action and any immediate response.
- At the freeze
- Visible message, animation state and displayed amount.
- Timing
- Approximate date, time and time zone.
- Environment
- Device, browser and connection type.
- Record reference
- A relevant round identifier, if available privately.
For example, saying that a spinner remained visible after a tap is stronger evidence than saying the server lost the round. The first is observable; the second is an unverified diagnosis.
Capture carefully
A screenshot can preserve an exact message, but it may also include an account name, balance, notifications or other private information. Review it before sharing and use a private official support route for sensitive identifiers.
Do not include passwords, one-time codes, full payment details or identity documents in an initial technical description. If a support process later requests verification, handle it through the service's established private process rather than a public discussion.
State the question clearly
Ask support to confirm the recorded status and outcome of the identified round. That is more useful than asking them to recreate every animation. A recovered interface may not replay the visual sequence even when a valid record exists.
Keep any follow-up under the same support reference where possible. Add newly discovered facts without rewriting the original observation. Until the recorded state is clear, avoid further play that would bury the incident beneath additional activity.