Reference simplefin chase stale fix

SimpleFIN / Chase Stale Feed Pattern

Chase accounts via SimpleFIN (MX aggregator) can silently stall while Bridge still reports status "OK". The balance-date field is the only real signal; if all Chase accounts share an identical frozen timestamp, the MX connection has lapsed.

Key facts: - All 4 SimpleFIN "orgs" (Justin Business + Personal, Krystal, Sip 'n' Serve, Gus) sit behind a single Chase login / one MX connection. - One Adjust click in Bridge refreshes all four simultaneously; you do not need to Adjust each org separately. - Bridge shows "Success!" even though nothing visibly changes on Chase's side; the re-poll happens in the background within minutes. - Chase grants expire periodically (~90 days). Bridge "OK" label is unreliable for Chase specifically.

Fix procedure: 1. Go to bridge.simplefin.org, log in. 2. Click Adjust (pencil icon) on any one Chase connection. 3. Wait a few minutes, then run systemctl --user start forge-finance-sync.service. 4. Confirm balance-date on Chase accounts moved past the frozen timestamp.

Detection: stale_feed alert fires daily per-institution while stale; it correctly fired Jun 10-13 before the fix. The stale alert not firing after a sync confirms recovery.

[Claude Code]

[auto-memory session 89084297-0012-4593-bc9b-788b617c6a30, confidence 0.88, mode direct]