In most cases, you should never need to force a resync — ThatApp's live sync keeps your lake current automatically. But if something looks wrong, here is how to trigger a manual sync.

When to force a resync

  • A record you know exists on the source platform does not appear in ThatApp
  • AVA's query results appear to be outdated
  • You reconnected a platform after a period of disconnection
  • Your platform shows data that does not match what ThatApp is reporting

Via AVA

"Force a resync of Podio." "Resync the Client Projects app in Podio."

AVA will confirm and initiate the resync. She will tell you when it is complete.

Via the Sync interface

Navigate to Sync → your platform. Click the Resync button at the top right. You can choose to resync the entire platform or a specific app.

What happens during a resync

ThatApp re-reads all records from the source platform and reconciles them with your lake. Records that exist in the source but not in your lake are added. Records whose field values differ are updated. Records in your lake that no longer exist in the source are marked as deleted.

A resync does not delete any of your lake history. It only adds or updates records.

How long it takes

For small platforms (under 10,000 records): under 5 minutes. For medium platforms (10,000–500,000 records): 30 minutes to 2 hours. For large platforms (500,000+ records): 2–8 hours.

You can continue using ThatApp while a resync runs. AVA will indicate when a sync is in progress.

Related: How Your Data Lake Works · Understanding Backup Behavior