Every connection exposes its own sync state so you can tell the difference between "no new subscriptions" and "no new data".
What the panel shows
- Last successful sync timestamp.
- Cursor progress — the provider position we have consumed, which advances as new transactions arrive.
- Recent errors with the provider reason and a suggested fix.
- Counts of transactions added, modified, and removed on the last run.
How syncing runs
- The bank notifies us when new transactions are available and the affected item is queued.
- A background worker processes the queue and runs detection over new transactions.
- A scheduled safety-net job re-syncs items that have not reported in, so a missed notification cannot silently stall your data.
Manual re-sync
Trigger a sync yourself from the connection card. Manual runs are rate-limited to protect provider quotas; if the button is disabled, a run is already in progress or one completed very recently.
Partial failures
When a batch sync touches several items and only some fail, the successful items still commit. The report lists each failed item with its reason and hint, so one broken connection never blocks the rest.
Timing expectations
Pending transactions can take one to three days to post at the bank. Flowarden can only see what the bank has published, so a charge you made this morning may not appear until it settles.