A saved setting, a device's last game reading and an action accepted by the game are three different states. Use this guide to identify where an operation stopped before repeating it or clearing any data.
Prepared by Travian Panel · Updated · Android, Chrome extension and web dashboard
When is an action actually complete?
Saving: Your edited setting or queued order must receive a successful save confirmation. Pending or rejected data is not confirmed data. Dismissing an error does not complete a save.
Sync: Devices signed into the same panel account retrieve server settings. Seeing an order on the website does not prove that the executing device has received it.
Game execution: The running app or extension checks the game session and action requirements. A construction or troop dispatch needs a verified game result before it is reported as completed.
For example, you add a building order online while the phone app is closed. The saved order alone does not prove that construction started. Check the executing device, the relevant activity log and the building in the game.
Check these six things before deleting data
Panel account: Check that the web dashboard and device use the same Google account. A panel account and a game account are different identities.
World and village: Compare the same world and village. Record the village name and identifier if a count differs.
Last check time: An old timestamp means the displayed count is from an earlier successful reading. Opening the panel does not by itself prove that a fresh reading completed.
Executing device: The app or extension must be available with a valid game session. Complete any additional game verification yourself.
One deliberate edit: Check the save confirmation before comparing the same setting on another device. Avoid changing it in several places during diagnosis.
Verified result: Compare the log message, check time and actual building or troop movement. Do not immediately repeat a dispatch whose outcome is uncertain.
Uninstalling the app or clearing its data should not be the first troubleshooting step. Reloading a device while a result is pending can also remove local evidence needed to understand the problem.
Common symptoms and what to check
Why do troop counts look old or different?
Troops at home and total own troops have different scopes. Total own troops can include units travelling or stationed elsewhere; the home view describes units currently in the village. Compare the scope and last check time first. Training queues do not count as completed troops.
Without Plus, the app can read the individual rally points to assemble the total. Reading several villages and movement pages can take longer than one overview page. Refresh requests a new check; it does not guarantee an instant result. If the check fails, the previous reading and its original timestamp remain available.
Why is a saved building order still waiting?
Check the selected village, construction permission, resources, building prerequisites and available queue space. Read the waiting reason in the activity log. Adding the same order repeatedly does not resolve missing resources or a full construction queue.
Why does another device show a different setting?
Compare the same village and field. If you change a training amount from 50 to 60, first confirm that the save succeeded. Account-wide switches and village-specific amounts are separate settings. A failed save does not prove that the new value reached the other device.
Why did a full warehouse not increase training?
The base troop amount, fullness threshold and increase percentage are separate settings. The relevant option must be enabled and the resources must meet its conditions when the task is evaluated. Compare the base amount with the evaluated task amount. The training planner in Turkish illustrates the resource arithmetic without connecting to your game.
What if the connection drops after a dispatch?
A dropped connection does not prove that the game rejected the action. Check outgoing and returning movements and the relevant log. If a movement exists, do not send the same order again. If the outcome is unclear, record the village, target and time for support.
What should I include in a support request?
Email aliorala@hotmail.com with your platform, app or extension version, world, village, expected result, actual result and error time. Include only the relevant log excerpt. Never send passwords, session cookies or sign-in codes; hide private information in screenshots.
Travian Panel is an independent product and is not an official Travian Games application. See product information and contact details. Check the game provider's current rules separately.