Tower Rush not working? Check round recovery, pending bets and refunds

Tower Rush not working when you open the game?

Check the route, game version and balance type first. If you’re opening the game from France, the real-money route is closed across all ten operator profiles examined. Betclic France is authorised for sports betting, horse-race betting and circle games such as poker. Its authorisation does not cover this game. You can check an operator’s permitted categories in the ANJ register.

The official FUN demo has separate desktop and mobile routes. If an embedded window stays blank, select the provider’s desktop or mobile demo on that page and check that the game shows a FUN balance. Confirm that the title is the original Galaxsys game. Tower Rush 2 is a separate game with its own history.

Tower Rush not working on your phone even though the right demo opens? Check whether the connection is stable and whether the problem affects loading, the controls or only the animation. A browser session and an operator app can use different game windows. See mobile access and apps to identify the client you opened before you try to recover a round.

An error about insufficient bonus balance points to the selected funds. The provider’s Free Bet mode tracks available free stakes, while Free Amount uses a bonus balance. If the error appears before acceptance, check which mode is active and whether the amount selected is covered in that mode. Keep FUN, operator bonus credits and cash separate when checking balances.

Recover an interrupted round by its original ID

Open the same game and check History for the original round before selecting Build again. To troubleshoot Tower Rush, use the recorded acceptance and balance movements to decide whether a stake was taken. The server determines the result. A weak connection or a device struggling to update the display can delay the animation and hide a result the server already recorded.

If Build timed out before you saw acceptance

Check for an accepted round and a matching debit before you act again. Tower Rush not working after you tapped Build? The screen can stop before it shows an acknowledgement, so a missing animation is a poor guide to whether the server took the stake. One accepted Build cycle starts with a single stake debit.

In the controlled pre-acceptance case, the debit was zero. Retrying the original request used the same request_id and checked the existing history before a new request could be created. As a player, you check the available history first. If you still can’t match the attempt to a debit or round, give support the time and stake so they can locate the original request.

If the stake was accepted before the disconnect

An accepted stake has a round record that you can recover under the same round_id. The request_id identifies the action you sent, while the round ID identifies the cycle whose outcome you want to recover. If your screen reopens on a fresh view of the tower, go to History and look for the old entry before taking another game action.

1. Record the stake, the local time and the round ID if it’s visible. Note the last action you took, such as Build or Cashout, and whether you saw it confirmed.
2. Reconnect and reopen the same version and mode. If the interruption happened in an operator session, use the same account and balance.
3. Open History. Match the original round ID, stake and time, then read the recorded status and any payout or refund.
4. Compare that entry with the debit and credit in the corresponding balance. For an operator round, ask support to reconcile the round and wallet if the two records disagree.

In one controlled FUN case, the server accepted 6.50 FUN and recorded a result at 1.8×. The recovered entry showed a gross payout of 11.70 FUN and a net result of +5.20 FUN after the stake. Reopening the round still showed a single payout. The gross figure includes the stake in this calculation, so adding the original debit back to the credit would overstate the return.

I also recovered the history after bringing the demo back from the background on a Samsung Galaxy S25 FE. The 18.50 FUN round showed a confirmed 1.55× and a gross credit of 28.68 FUN after rounding, giving a net result of +10.18 FUN. The history entry let me match the credit to the original round when I returned to the game window.

Under Galaxsys’s rules, if the connection stays down after acceptance, the round ends after one hour of inactivity. Any win the server has already registered is credited automatically.

When you return, read the settlement to see how the round closed.

If Cashout or the result reappears after settlement

A round that has already settled keeps its original settlement. In the controlled case where a protected payout had reached the cap, repeating the last request returned the existing settlement_id and final status. A result shown again after reconnecting can therefore correspond to the credit already in your balance.

Check whether Cashout was confirmed before the round ended. A tap on the button can appear on your screen before the server responds. Once the server has settled a collapse, sending Cashout again produces no additional payout. The game rules explain how the original game handles a collapse and any protection already earned.

Pending stakes, void rounds and refunds

Pending means the accepted stake still has an unresolved settlement. In a controlled demo case, the pending entry carried a 13.00 FUN obligation. When the round moved to void, the 13.00 FUN refund cleared it. The final obligation and net result were both zero, and the round added zero to comparable turnover. Read the refund and the original stake together to see what changed.

Galaxsys’s rules provide for cancellation of the affected bets and payouts when game equipment or software malfunctions, with the original stakes returned. A network interruption has its own recovery rule. Check the recorded status before drawing a conclusion from either a frozen screen or the passage of time.

A settled Cashout can also leave the balance unchanged. In my demo session, a 5.00 FUN stake cashed out at 1× and returned 5.00 FUN as gross payout. The net result was zero, with the stake counted in turnover. Check the type of credit when the amount alone could fit either a payout or a refund.

In that mobile session, I recorded one technical cancellation among 24 accepted rounds. That round debited 4.00 FUN and lowered the balance from 763.90 to 759.90 FUN. The 4.00 FUN refund brought it back to 763.90 FUN, with zero gross winnings. The other 23 rounds settled. The session therefore had 254.00 FUN in stake debits and 250.00 FUN in comparable turnover once the void was excluded.

Who to contact when the records disagree

Contact the operator for an account or wallet discrepancy in an operator session. Give support the game version, original round ID, stake and unit, local time with time zone and last action. Describe the events around the interruption, including what happened before and after any confirmed acceptance. Include the status in History and any recorded payout. If the case is reopened, use the same round ID and keep the same chronology. Keep your password, session token and card number out of the message.

Two French-language support exercises illustrate the difference between repairing history and correcting the balance. In the queue case, an acknowledgement arrived in 8 seconds and a substantive reply in 8 minutes. History was restored after 22 minutes. The original payout was already present, so the financial adjustment was €0.00.

In the email case, the acknowledgement took 24 seconds and the first substantive reply took 22 minutes. A second-line duplicate check preceded the correction at 44 minutes. I checked the separate control ledger. A €3.00 debit took a €20.00 balance to €17.00. One €7.20 credit brought it to €24.20, and rereading the ledger left it there. These timings describe the individual exercises. The euro entries belong to the control cases and are separate from the FUN demo.

For a dispute about a product authorised in France, raise it with the operator first. If it remains unresolved, check the ANJ dispute and mediation process for the applicable conditions. Send errors in the wording on Tower Rush France to the editorial team. The editorial channel handles French and English. In a separate exercise, the first substantive reply came after 1 hour 53 minutes and the team corrected the label for Tower Rush 2. The correction involved no wallet movement.

Choose the next step

Reopen the FUN demo if the launch window failed. If you were already in an accepted round, go back to its History entry before making another attempt. Use account recovery if you can’t reach the original operator session. If the game credit is already recorded and your issue is with a separate transfer, check the withdrawal stages.

FAQ