Cloud Sync and what syncs where
How profile, health and broker data reach your account, and how to investigate devices showing different data.
On this page
What syncs to your account
Profile changes sync when saved. Health data syncs through the configured health connection. Broker history comes from broker sync or a supported file import. These are separate paths, with their own permissions, connection state and results.
The Cloud Sync entry or last-synced timestamp on an installed app is not a manual backup of all local work. In particular, it does not upload a local trade or open-position copy as canonical broker history, and it cannot restore another device’s missing trades from that copy. Background work is subject to the operating system; it has no guaranteed fixed completion time.
When two devices disagree
- Check that both devices are signed into the same VEXA account.
- Compare account filters, dates and the view you are looking at.
- Read the actual broker sync or file-import result. Use the broker’s supported sync/import route for missing history.
- Refresh the affected view and check its error or unavailable state.
- For missing health data, check the health connection, permissions and source app. Health readings are synced to your account for VEXA features; they are not device-only data.
If the discrepancy remains, contact support with the device, view and sync/import result. A changing timestamp by itself does not establish complete history.
Before signing out
Keep any unsent draft open and confirm it has saved before signing out. Signing out can clear local state; a Cloud Sync timestamp is not proof that an offline edit or draft was saved. Do not sign out or discard a draft as the first step to repair a missing-trade display.
Related controls
Related
Still stuck? Email support@vexatrade.ai.