Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.redbark.co/llms.txt

Use this file to discover all available pages before exploring further.

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.
Run statusDescription
RunningA sync is in progress
SuccessThe run completed
FailedThe run encountered an error
Per-account statusDescription
SuccessRecords were processed for the account
FailedThe account failed during this run
No dataThe account returned no new records

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, retry count) 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
The sync list also marks the row with a Needs attention status pill so broken syncs are visible without opening each one.

Re-running a sync

Use Sync Now on the sync detail page to trigger an immediate run. The button is disabled while the sync is inactive. To recover after a bank-side outage or expired consent, reconnect from the Connections page — that triggers the affected syncs once the connection is healthy again.