# TimeoutAction

TimeoutAction defines the action to take when a timeout occurs if a scaling point is not found.

- Source: [`aws-rds/lib/serverless-cluster.ts`](https://github.com/aws/aws-cdk/blob/v2.275.0/packages/aws-cdk-lib/aws-rds/lib/serverless-cluster.ts#L272)
- Type last changed: v2.118.0 · 3 Jan 2024

## Example

```ts
declare const vpc: ec2.Vpc;

const cluster = new rds.ServerlessCluster(this, 'AnotherCluster', {
  engine: rds.DatabaseClusterEngine.AURORA_POSTGRESQL,
  copyTagsToSnapshot: true, // whether to save the cluster tags when creating the snapshot. Default is 'true'
  parameterGroup: rds.ParameterGroup.fromParameterGroupName(this, 'ParameterGroup', 'default.aurora-postgresql11'),
  vpc,
  scaling: {
    autoPause: Duration.minutes(10), // default is to pause after 5 minutes of idle time
    minCapacity: rds.AuroraCapacityUnit.ACU_8, // default is 2 Aurora capacity units (ACUs)
    maxCapacity: rds.AuroraCapacityUnit.ACU_32, // default is 16 Aurora capacity units (ACUs)
    timeout: Duration.seconds(100), // default is 5 minutes
    timeoutAction: rds.TimeoutAction.FORCE_APPLY_CAPACITY_CHANGE // default is ROLLBACK_CAPACITY_CHANGE
  }
});
```

## Members

| Member | Description |
| --- | --- |
| `FORCE_APPLY_CAPACITY_CHANGE` | FORCE_APPLY_CAPACITY_CHANGE sets the capacity to the specified value as soon as possible. |
| `ROLLBACK_CAPACITY_CHANGE` | ROLLBACK_CAPACITY_CHANGE ignores the capacity change if a scaling point is not found. |

## Referenced by

- [`ServerlessScalingOptions`](/v2/docs/aws-cdk-lib.aws_rds.ServerlessScalingOptions).timeoutAction