# Amazon SES "Configuration set sending is paused": Causes and Fix

Source: https://wraps.dev/ses/errors/configuration-set-sending-paused

Account and configuration set stateConfigurationSetSendingPausedException

Why SES pauses sending for one configuration set while the rest of the account keeps sending, and how to resume it.

## The error

```
Email sending is disabled for the configuration set <ConfigurationSetName>.
```

AWS exception `ConfigurationSetSendingPausedException`. The Wraps CLI reports it as `SES_CONFIG_SET_SENDING_PAUSED`.

## Why this happens

Sending is paused for the specific configuration set this send named, not for the account. That is the useful part. It means the rest of the account is still sending, and the pause is scoped to whatever traffic routes through this configuration set.

-   Sending was disabled on the configuration set, by you or by an automation.
-   A reputation option on the configuration set paused it automatically when its own bounce or complaint rate crossed a threshold.

## How to fix it

1.  ### 1. Confirm the scope before you change anything
    
    Read the configuration set's sending status and the account's separately. A paused configuration set and a paused account need different responses, and the exception name tells you which one you have.
    
    ```
    aws sesv2 get-configuration-set --configuration-set-name <name>
    ```
    
2.  ### 2. Resume it in the SES console
    
    Under Configuration Sets, re-enable sending for the set. Do this after you know why it paused, not before.
    
3.  ### 3. Or send without the paused configuration set
    
    Removing ConfigurationSetName from the request gets the mail out. It also removes the event publishing that set was feeding, so treat it as a stopgap rather than the fix.
    
4.  ### 4. Check the automatic pause option
    
    A configuration set can be configured to pause itself on reputation metrics. If that is what fired, resuming without addressing the metric just pauses it again.
    

## How to stop it recurring

### Separate traffic types by configuration set

Putting campaigns and transactional mail on different configuration sets means a reputation problem in one does not stop the other. That separation is what makes a scoped pause survivable.

### Alert on the configuration set, not only the account

Account-level dashboards average over everything. A single configuration set can be in trouble for a while before it shows up in the account number.

## Common questions

### Is a paused configuration set the same as a paused SES account?

No. A configuration set pause stops only sends that name that set. An account pause stops everything. AWS uses different exceptions for the two so you can tell them apart in code.

### How do I resume sending for an SES configuration set?

Re-enable sending for the set in the SES console under Configuration Sets. Find out why it paused first, especially if it paused itself on reputation metrics.

### Can I just remove the configuration set from the send?

It will deliver the message, and it will also stop the event publishing that configuration set was feeding. Useful to unblock, not something to leave in place.

## What Wraps does about this

The Wraps CLI maps this exception to SES\_CONFIG\_SET\_SENDING\_PAUSED and keeps it distinct from the account-level pause, which is the distinction that decides what you do next. Resuming the configuration set is a change in your AWS account and stays yours to make.