Skip to content
NewinZora in your browser
Zora in your browser

After a connection drop, establish the last accepted action

When a Zora game loses connection, the first task is to establish what happened before the interruption.

4 min read
01

Identify the last known action before the interruption

When a Zora game loses connection, the first task is to establish what happened before the interruption. A disconnected screen cannot tell you by itself whether the last stake reached the game service. Separate the device's visible state from the transaction that may already have been accepted.

The useful starting point is the last event you can actually confirm. Did you only change a stake field, press start, receive an acceptance message or see a completed result? These stages have different implications. A phone that loses the picture after acceptance is not in the same situation as a page that never submitted a request. Write down the observed stage rather than assuming failure or success. The missing screen is evidence of an interruption, not a complete account of the transaction.

02

Restore the connection without adding new actions

Stop pressing controls and note the approximate time, title and last action. Restore an ordinary stable connection without trying to bypass location restrictions. When the game becomes available again, read any recovery message and inspect the relevant history. Do not assume every provider restores an unfinished round in the same way.

Once the device has a normal connection again, return to the intended account and read the game’s recovery message if one appears. Avoid opening several duplicate game windows at the same time, because they can show different snapshots and confuse the sequence. Do not clear local data as the first move when the page still contains an error or reference worth preserving. The provider’s rules and recorded state determine the round’s handling; there is no universal promise that every game restores its animation in the same way.

03

Reconcile intention, acceptance and balance movement

Compare three records: the stake you intended, the accepted round entry and the resulting balance movement. An animation that resumes may help explain the result, but the animation alone is not the transaction record. If no round reference appears and the balance is unclear, ask support to check the event before repeating the stake.

The intended amount tells you what you tried to do; the accepted round entry tells you what was recorded; the ledger shows the financial movement. Compare all three rather than using one changing header total. A game return can include the stake under its own display convention, so the credited amount is not always the net profit. Match the round identifier where available. If the account record and game display disagree, retain both observations and ask about the specific event without placing another stake as a diagnostic test.

04

Consider both possible states of an interrupted request

For example, a phone can lose its connection just after a start tap. The round might have been accepted before the connection failed, or the request might not have arrived. These possibilities require checking the record; neither can be settled merely by the absence of a result on the phone. A second start tap could create a separate action.

Imagine a start tap immediately followed by loss of connection. The request may have reached the game before the interruption, or it may not have reached it. Neither outcome follows automatically from the absent animation. Repeating the tap after reconnection could therefore create a second round. Check the history first and identify whether the original attempt has an accepted entry. If the interface supplies no clear record, the appropriate next step is a question about that timestamp and game, not an assumption that the stake was cancelled.

05

Preserve the evidence before changing local data

Keep the error wording and avoid clearing site data until you have captured the details. If the issue remains unresolved, provide the account's available round reference and the interruption time. A connection failure is a technical event, not automatic evidence of either a lost stake or a promised refund.

Keep the exact error, approximate interruption time, title, provider and any round reference. State whether the connection changed, the phone locked or the browser closed. Share only the account information necessary through the official support route. If clearing site data later becomes part of an explained troubleshooting step, preserve the evidence beforehand and understand that local settings may be removed. A connection failure does not itself prove a refund entitlement or an incorrect outcome; the investigation needs the accepted action and its recorded settlement.