Reconnect an expired connection

<h2>How you find out</h2><p>Three things happen when a token stops working, and you will usually notice the third one first. The connection turns amber on the Connections page. Every flow using it pauses rather than failing record by record. And an email goes to the workspace owner and to whoever built the flow, once, not once per run.</p><p>Pausing is deliberate. A flow that kept trying against a dead token would burn through retries, fill your run history with noise and, on some apps, get the whole account rate limited for everybody. A paused flow holds its place and waits.</p><h2>Reconnect in five steps</h2><ol><li><strong>Open Settings, then Connections.</strong> Sort by health and the broken one sits at the top with the reason beside it.</li><li><strong>Read the reason before you click anything.</strong> <em>Token revoked</em> means somebody removed the app on the provider side, and reconnecting will fail again in a minute unless that person knows. <em>Token expired</em> is routine and reconnecting is enough.</li><li><strong>Click Reconnect.</strong> You go back to the provider's sign in screen. Use the same account as before. A different account creates a second connection rather than repairing this one, which is the most common mistake here.</li><li><strong>Re-approve the same scope.</strong> If the provider asks which pages, bases or boards to share, tick the same ones. A narrower selection reconnects cleanly and then fails later with a missing resource error, which is much harder to diagnose.</li><li><strong>Test, then resume.</strong> Click <em>Test connection</em>, and when it comes back green use <em>Resume all</em> to restart every paused flow at once.</li></ol><blockquote><p>Note: reconnecting never changes a field mapping. The flows come back exactly as they were, pointing at the same channels, boards and databases, so there is nothing to rebuild afterwards.</p></blockquote><h2>Replaying what you missed</h2><p>Records created while a flow was paused are not lost, they were simply never read. After you resume, open the flow and use <em>Backfill</em> to sweep a window of up to seven days. Syncline reads matching records from that window and runs them through as normal, applying the same filters and the same duplicate matching.</p><p>Backfilled records count as tasks. On a busy trigger, check the estimated count that the backfill dialog shows before you confirm it, because a week of a noisy database can be a large number.</p><h3>Why connections expire</h3><table><thead><tr><th>Cause</th><th>Usually affects</th><th>How to avoid it next time</th></tr></thead><tbody><tr><td>Password change</td><td>Gmail, HubSpot</td><td>Use a shared account with a stable password</td></tr><tr><td>Admin revoked the app</td><td>Slack, Notion</td><td>Ask IT to allowlist Syncline once</td></tr><tr><td>Token rotation policy</td><td>Airtable personal tokens</td><td>Move to OAuth, which refreshes itself</td></tr><tr><td>Account deactivated</td><td>Any</td><td>Reconnect under a shared address</td></tr><tr><td>Board or base deleted</td><td>Trello, Airtable</td><td>Point the flow at the replacement</td></tr></tbody></table>