Skip to main content
Before trusting an inventory, sales, or pull-session answer, check how fresh the underlying Hoard data is. Sync health is a read-only seller job: it reports the condition of the connection without starting work. First connect your assistant. For the client-agnostic path, see how to connect an AI assistant to your store, or follow the setup for Claude, ChatGPT, or Codex.

​
Step 1: Ask

“Is my Hoard sync healthy? Tell me the last sync time, whether one is in progress, the last outcome, and the next safe action. Do not trigger a sync.”
The assistant calls Hoard’s sync-health read surface. It can return a verdict such as healthy, sync in progress, agent offline, sync failing, sync stale, read-only warning, or no history, alongside the last-sync and desktop-agent state. It does not start a sync, change a pricing rule, or update TCGplayer.

​
Step 2: Read the answer

Expect the last successful sync time, whether a sync is currently in progress, the last outcome, and a next-action hint. The answer describes the data Hoard has; it does not prove that TCGplayer has accepted every later price push or that the desktop agent can complete a future sync.

​
Step 3: Decide whether to act

Checking status never changes anything. If the result is stale or failing, first read the stated condition and fix the local cause if one is shown. Requesting a fresh pull is separate: see trigger a TCGplayer sync. That is a write action, and you should only use it after this check shows it is needed.

​
If it looks stuck

A sync that stays in progress or keeps failing is not something the assistant can repair by itself. The health result may identify an offline agent, stale data, or a read-only warning, but it does not replace the desktop-agent diagnosis. Work through fixing a sync that’s actually stuck before repeatedly requesting new syncs.