SendOps regularly syncs with your connected AWS SES account to keep your dashboard in sync with what's actually configured in SES. This runs automatically in the background — no action needed on your part.

## What gets synced

Each sync checks your AWS SES account for:

- **Domains** — domain identities configured in SES
- **Email identities** — individual email address identities
- **Channels** — SES configuration sets mapped to SendOps channels
- **Contact lists** — your SES contact list, its topics, and subscribers (synced on its own hourly schedule and immediately on first connect)

The sync detects three kinds of changes:

| Change | What it means |
|---|---|
| **Discovered** | A new identity or configuration set was found in your SES account that SendOps wasn't tracking. It appears in your dashboard with a "New" badge for the first 7 days. |
| **Detached** | An identity or configuration set that SendOps was tracking no longer exists in your SES account. It's marked as "Detached" so you can decide what to do with it. |
| **Reattached** | A previously detached identity reappeared in your SES account. SendOps automatically marks it as active again. |

## Viewing sync history

Open the **AWS Status Badge** in the dashboard header and click **History** next to "Last sync" to see a history of all sync runs. Each entry shows:

- **Date / Time** — when the sync ran
- **Trigger** — whether it was a scheduled sync or manually triggered
- **Status** — Completed, Running, Failed, or Queued
- **Discovered** — number of new entities found
- **Detached** — number of entities no longer found in SES
- **Reattached** — number of previously detached entities found again
- **Updated** — number of entities with changed attributes

## Triggering a manual sync

Click the **Sync Now** button on the Sync History page to trigger a sync immediately. After a manual sync, there is a short cooldown before you can trigger another one.

## Entity lifecycle

Every domain, email identity, and channel in SendOps has a lifecycle state that reflects its relationship to your AWS SES account:

| State | Meaning |
|---|---|
| **Active** | The entity is in both SendOps and your SES account. Everything is in sync. |
| **Discovered** | The entity was found in your SES account during a sync but hasn't been managed in SendOps before. Shows a "New" badge for the first 7 days. |
| **Detached** | The entity was previously active in SendOps but is no longer found in your SES account. You can archive it or wait for it to reappear. |
| **Archived** | You've manually archived this entity. It's hidden from the default list view but can be restored at any time. Archived entities are not affected by sync. |

### Archiving and restoring

When an entity becomes **Detached** (no longer found in SES), you can **Archive** it to remove it from your default view. Archiving does not delete anything from SES — it simply hides the entity in SendOps.

SendOps also **auto-archives** entities that have stayed detached for **30 or more days**, so long-gone identities and channels don't clutter your view forever. You can still restore them afterwards.

To view archived entities, enable the **Show archived** toggle on the Channels or Identities page. From there, you can **Restore** any archived entity to make it visible again.


  **Archive** hides an entity from your dashboard without affecting SES. You can restore it later. **Delete** permanently removes the entity from both SendOps and your AWS SES account. Use archive when you want to clean up your view; use delete when you want to remove the identity from SES entirely.


### Detaching a channel manually (shared AWS accounts)

The **Detached** state above is driven by sync — it appears when a configuration set genuinely disappears from SES. There is also a separate, **user-initiated Detach** for channels, meant for **shared AWS accounts** where more than one SendOps workspace connects to the same SES account.

Because sync discovers every configuration set in the account, a workspace will see channels that actually belong to a sibling workspace. Using **Detach** on such a channel hides it from your view **without changing anything in AWS**. This kind of detach is **sticky**: since the configuration set still exists in SES, SendOps will *not* auto-reattach it on the next sync, and the 30-day auto-archive sweep leaves it alone. Use **Reattach** to undo it and return the channel to the **Discovered** state.

See [Managing Channels](/channels/managing-channels#detaching-and-reattaching-a-channel) for the full walkthrough.


  When two or more workspaces both claim the same identity and neither has adopted it, its analytics events are **paused** (not lost) until you resolve the conflict. See [Shared AWS Accounts & Claim Conflicts](/aws-setup/shared-accounts) for how to resolve them and how paused events are replayed.


## What's next?

- Learn how domains and email identities are managed on the [Identities](/domains/adding-a-domain) page.
- Learn how channels map to SES configuration sets in [Understanding Channels](/channels/understanding-channels).