> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nylon.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# An account says Reconnect

> What makes a connection stop working, how to clear it, and what your application should do in the meantime.

A profile showing **Reconnect** — `status: needs_attention` in the API — means the credential Nylon holds for it no longer works. Publishing to it fails with `reauthentication_required` until someone authorizes it again.

Nylon refreshes tokens continuously, so this is almost never an expiry it could have prevented. It is a credential that was revoked on the network's side.

## Why it happens

In rough order of how often:

1. **Someone changed the account's password.** Most networks invalidate every issued token when a password changes.
2. **Nylon was removed from the account's connected apps.** Either deliberately, or during a security tidy-up nobody connected to your integration.
3. **Page or account administration changed.** A Facebook Page whose admin was removed, or a Business Manager reshuffle, invalidates access granted through the old administrator.
4. **The account changed type.** An Instagram account converted back to personal cannot be published to at all.
5. **Your own OAuth app changed.** Only if the profile's **OAuth app** column says *Your app* — rotating or deleting a BYOK client secret breaks every profile connected through it. See [Configure BYOK](/help/configure-byok).

## Clearing it

Open **Connections**, find the row, and select **Reconnect** from the **⋯** menu. Sign in with the account that administers the profile and approve every permission.

The full walkthrough, including what to do when reconnecting does not stick, is in [Reconnect an account](/help/reconnect-an-account).

## Be told before your users are

Do not poll the profiles endpoint. Subscribe to `profile.needs_attention` and Nylon calls your server the moment a credential stops working — which is usually hours or days before the next scheduled post would have revealed it.

A good handler does three things:

<Steps>
  <Step title="Mark the account in your own database">
    So your UI can show it, and so you stop scheduling against it.
  </Step>

  <Step title="Tell the user, with a link that fixes it">
    Generate a connection URL from the API and put it behind a button in your own product. Sending them to the Nylon dashboard is not an option if they do not have a Nylon login.
  </Step>

  <Step title="Clear the warning on profile.connected">
    That event fires on a reconnection too, so it doubles as the "they fixed it" signal.
  </Step>
</Steps>

## What happens to scheduled posts

A post scheduled against a profile whose credential has failed will fail when its time comes. Nylon does not hold it back, and it does not retry it afterwards — fixing the connection does not republish anything.

If a post matters and its account needs reconnecting, reconnect first and then re-schedule.

## Related

<Columns cols={2}>
  <Card title="Reconnect an account" icon="refresh-cw" href="/help/reconnect-an-account">
    The step-by-step, and why a reconnect sometimes does not take.
  </Card>

  <Card title="Webhook events" icon="webhook" href="/help/webhook-events">
    Subscribing to account status changes.
  </Card>
</Columns>