# Up to 5 million running executions! Lambda durable functions raises default quotas

Hi everyone, it's Shii-chan! Today AWS raised the quotas for Lambda durable functions.

## What was announced?

According to AWS What's New, **AWS Lambda durable functions** has increased its default quotas for running executions and API request rates.

Lambda durable functions helps you build resilient multi-step applications and AI workflows that run for up to one year, with built-in checkpointing, automatic retries, and waits that suspend execution without compute charges.

## The story so far

The lower default quotas meant that running a very large number of executions in parallel could require a quota increase request.

## What changes

- Workloads such as order processing and document pipelines can run more executions in parallel without quota requests
- When many executions wait on external work like payment confirmations or batch jobs, more can resume together
- Dashboards and scripts can check status, list executions, read history, and stop executions at least ten times as often

## Dive Deep

The new default quotas:

- Running durable executions per account: 1 million to 5 million
- Function invocation rate to start durable executions: 300 to 3,000 requests per second
- CheckpointDurableExecution and GetDurableExecutionState: 1,000 to 10,000 requests per second
- SendDurableExecutionCallbackSuccess, Failure, and Heartbeat: 300 to 3,000 requests per second
- GetDurableExecution and StopDurableExecution: 30 to 300 requests per second
- GetDurableExecutionHistory and ListDurableExecutionsByFunction: 15 to 150 requests per second

These apply in all AWS Regions except US East (N. Virginia), US West (Oregon), and Europe (Ireland), which have twice these quotas.

## Wrap-up

- Up to 5 million running durable executions
- About 10x higher API rates
- Three major Regions get double the quotas

This is for anyone running large workflows on Lambda durable functions!