Pause input immediately
If the connection disappears during a round, stop tapping the game controls. A delayed response can arrive after the screen appears inactive, and repeated taps may create ambiguity. Do not assume that no visible animation means no action was accepted.
Note what was visible when the interruption occurred: a connection message, a spinning indicator or a settled amount. These observations help describe the display, but they do not independently establish the server's recorded outcome.
Check connectivity without another round
Look at the phone's network indicator and determine whether the device has lost all connectivity or only the page has reported a problem. A successful unrelated page load can indicate general access, but it cannot prove that the game session is healthy.
Avoid rapidly switching between wireless and mobile data while also reloading the game. That changes several conditions at once and makes troubleshooting less clear. Restore a stable connection first, without using paid game actions as tests.
Make a small incident record
Record enough information to distinguish the affected round from surrounding activity. Keep private account details out of notes that might later be shared publicly.
- Approximate time and time zone.
- Game name as displayed.
- Exact connection message, if readable.
- What action immediately preceded the interruption.
- Any visible round identifier.
If taking a screenshot, inspect it for balances, account names and unrelated notifications before sharing. An identifier should go only through the appropriate private support route.
Verify before resuming
When stable access returns, inspect available recorded round history or the service's recovery instructions. A recovered animation may not replay every visual step, so use the recorded status and amounts rather than requiring the original sequence to finish on screen.
If history is missing, contradictory or marked unresolved, stop. Contact support with the incident record instead of initiating another round to see whether the account behaves normally. A new deposit is not a technical recovery step.
Understand the limits of local checks
Airplane mode, browser restarts and network changes affect the device. They cannot determine an unknown server-side outcome by themselves. Clearing browser storage may also remove useful session context and should not be the first response to an unsettled round.
Once support or the recorded history clarifies the state, decide separately whether to continue at all. Restoring connectivity solves an access problem; it does not create an obligation to resume or recover anything through further play.
A brief interruption can be frustrating, but urgency does not improve the quality of verification. Keep the original incident details intact until the question is resolved.