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

# Delete and archive

> Retire a connection. It stops syncing and moves to the archive for history.

Retiring a connection is a single action: **Delete**. It stops all sync jobs and moves the connection to your **Archive**, where it's kept for history along with the reason you gave.

<Note>
  Deleting is a **soft** action. The connection leaves your active list but is retained in the Archive as a record — it isn't wiped. The in-app confirmation is worded strongly ("permanently delete… cannot be undone") because it stops syncing and there is no self-serve restore, but the connection and its reason remain visible in the Archive.
</Note>

## What deleting does

* **Stops all sync jobs** immediately. The connection no longer reacts to source changes, schedules, or manual runs.
* **Moves the connection to Archive**, tagged with the reason you entered.
* **Leaves your Webflow CMS items in place.** The items this connection created stay in your site — nothing will update them again.
* **Leaves your Airtable data untouched.**

## What deleting does not do

* It does **not** delete the CMS items in Webflow.
* It does **not** touch your source data.
* There is **no in-app restore** today. The Archive is a read-only history. To sync the same source and collection again, create a new connection.

## Delete a connection

<Steps>
  <Step title="Open the connection">
    Go to the connection's detail page.
  </Step>

  <Step title="Find the Danger Zone">
    Scroll to **Danger Zone** and click **Delete**.
  </Step>

  <Step title="Read the confirmation">
    *"This will permanently delete `<connection name>` and stop all sync jobs."* In practice the connection is retained in your Archive — but syncing does stop.
  </Step>

  <Step title="Type the exact name">
    Character for character. This guards against retiring the wrong connection.
  </Step>

  <Step title="Give a reason">
    Free text, required. It's stored with the connection and shown in the Archive.
  </Step>

  <Step title="Confirm">
    The connection stops syncing and moves to Archive.
  </Step>
</Steps>

<Warning>
  Both the **name** and the **reason** are required — the confirm button stays disabled until both are filled.
</Warning>

## The Archive

Retired connections live under **Archive** in the sidebar. It's a read-only list showing each connection and the reason it was retired — useful for auditing what once synced into a collection and why it was stopped.

The Archive doesn't sync anything and doesn't block other actions.

## When you have to delete

Two situations in the app require retiring a connection first:

<AccordionGroup>
  <Accordion title="Reusing a Webflow collection">
    A Webflow collection can back only one live connection. To point a different source at a collection that's already connected, delete the existing connection first.

    *"Webflow collection already connected — Delete the existing connection for this Webflow collection before creating another one."*
  </Accordion>

  <Accordion title="Disconnecting a data source">
    An account can't be disconnected while a live connection depends on it. Delete the dependent connections first — once archived, they no longer block. The dialog lists up to five blockers.

    *"Delete active connections before disconnecting this data source."*
  </Accordion>
</AccordionGroup>

## Before you delete

<Steps>
  <Step title="Check what depends on it">
    Deleting leaves the CMS items in place but stops updating them. If this connection is the only thing keeping a collection current, its content will go stale.
  </Step>

  <Step title="Note the configuration">
    Mapping, direction, and per-field ownership go with the connection, and there's no restore. Rebuilding a large mapping by hand is tedious — capture it if you might need it again.
  </Step>
</Steps>