Skip to main content
Sync history lives on each sync’s detail page, not on a dedicated /runs route. Open a sync from Syncs and click View to see its run history.

​
Activity Feed

The detail page shows an Activity Feed beneath the Connections and Destination cards. Each entry represents one sync run, with one row per account showing how many records were added, updated, or deduped, plus the run duration. The feed is capped at roughly the most recent 25 entries (recent runs with many accounts may consume more of that budget).

​
Statuses

Runs have a top-level status and a per-account event status.

​
Webhook deliveries

Webhook syncs have an extra Deliveries tab on the sync detail page. It shows up to 50 of the most recent HTTP delivery attempts (status code, response time, payload size, error message) for the webhook destination.

​
Needs attention

When a sync fails for a reason the user can fix, the detail page shows a Needs attention banner above the cards. Categories include:
  • Destination authentication expired — re-authorize the destination
  • Bank connection lost — reconnect the bank from Connections
  • Bank consent expired or withdrawn — reconnect from Connections to start a fresh consent
  • Sync configuration error — open the sync settings to resolve
  • Destination resource deleted — the target spreadsheet, budget, or webhook was removed
  • Data error — the run failed validating provider data
  • Partial write failure — some rows could not be written to the destination; re-run the sync to retry them
The sync list also marks the row with a Needs attention status pill so broken syncs are visible without opening each one.

​
Automatic waiting and recovery

When a banking provider or destination temporarily limits requests, the sync list shows Waiting. Redbark keeps the work scheduled and retries automatically, so you do not need to reconnect or repeatedly press Sync Now. The last successful sync time remains visible while it waits. A wait only becomes a failure if automatic recovery cannot complete.

​
Re-running a sync

Use Sync Now on the sync detail page to trigger an immediate run. If work is already scheduled, the request joins it instead of starting another run. The button is disabled while the sync is inactive. Reconnect from the Connections page only when the connection or consent needs attention; temporary provider waits recover automatically.