HelpKeys and security
Why a sync failed and what to do
A failed sync usually means a revoked or expired key or an exchange outage. TrueHold retries, emails you if it keeps failing, and lets you re-connect.
Each exchange account shows its sync state: awaiting first sync, queued, last sync failed and retrying, or up to date. Most failures resolve on the next retry without you doing anything.
When it keeps failing
- 01Check the key on the exchange. A revoked, expired or permission-changed key is the most common cause. Replacing it from the account settings fixes it.
- 02Check the exchange. Venue outages and maintenance windows stop reads until the venue is back; the retry picks up automatically.
- 03Re-connect the key from the account settings if the state says re-connect. Validation runs again before anything is stored.
TrueHold sends an email when a sync fails persistently, so a broken key does not sit unnoticed. That email, a new-login notice and the welcome message are the only emails the product sends.
Related
Replace or rotate an API key
Open the exchange account in TrueHold, replace the key from its settings, and the account keeps its history. Expiring keys are flagged in advance.
Connect an exchange with a read-only API key
Create a read-only key on the exchange, paste it into TrueHold, and balances, positions and history appear. The key is validated before it is stored.
Emails TrueHold sends
Three emails exist: a welcome message, a new-login notice, and a warning when a sync keeps failing. No newsletter, no marketing mail.
Still stuck?
Write to hello@truehold.xyz with the screen you are on. Answers become docs, so the next person finds it here.