When your devices don't agree

Two devices showing different numbers is almost always a timing problem, not a data problem: one of them hasn't heard the news yet. Climb is local-first, so each device works from its own copy of your budget and the server keeps those copies in agreement.

The design itself is covered in Offline, local, and in sync; this article is for when it looks like it isn't working.

Give it a moment online

Changes made offline queue up on the device and upload the next time it's connected, usually within seconds. So the first check is the boring one: does the device that looks behind actually have a connection, and has the app been opened since? A phone that's been in your pocket all day hasn't synced all day.

Same account, same budget

If the two devices look completely different rather than slightly behind, check that they're signed into the same account and looking at the same budget. Budgets are listed on the Budget page in Settings; a restored backup becomes its own separate budget, which is a common way to end up comparing two different things without realizing it.

Same transactions, different totals

If both devices show the same transactions but a category's remaining differs, the derived math on one of them has drifted. Each device keeps its own cached running totals, so run Recalculate balances (Settings, Data page) on the device that looks wrong. When a number looks wrong covers this in more detail.

Editing the same thing in two places

If the same transaction or budgeted amount is edited on two devices before they've had a chance to sync, the most recent edit wins and the other is overwritten. In normal use this is rare; it matters mostly if two people budget together on separate devices at the same moment. When in doubt, pause a beat and let the numbers settle before making the same edit twice.