Agent Operating Guide
/bridge-sync-status
Read-only operational view across all configured bridges: sync log, open conflict queue, and last pull and push time per bridge.
See how your bridges are doing at a glance. This read-only view walks every configured bridge and renders a status table, last push, last pull, recent push and pull errors, and the count of open conflicts, so you can tell whether sync is healthy, whether conflicts are piling up, and when each bridge last succeeded. It reads sync logs and config only and changes nothing.
When to use
Section titled “When to use”To check bridge health: after a sync run, before relying on synced data, or on a schedule to catch a bridge that has quietly stopped or is accumulating conflicts.
Inputs
Section titled “Inputs”| Flag | Required | Notes |
|---|---|---|
--bridge <name> |
No | Limit to a single bridge. Defaults to all. |
--format <kind> |
No | table (default) or json for a dashboard or scheduled check. |
Example
Section titled “Example”/bridge-sync-status prints one row per bridge, Archer, ServiceNow, Workday,
AuditBoard, with its last push and pull times, 7-day push and pull error
counts, and open-conflict count. --bridge archer narrows to one bridge;
--format json returns the same data as JSON.
Good to know
Section titled “Good to know”- A bridge that’s configured but hasn’t synced within its expected cadence is flagged stale, so a silently-stopped sync doesn’t go unnoticed.
- Run it on a schedule to monitor sync health proactively.
Related
Section titled “Related”- /bridge-archer-sync: one of the syncs this view monitors.
- /bridge-snow-sync: the other sync it monitors.
- /bridge-conflict-resolve: triages the open conflicts this view counts.