What would you like?
Currently, there is no built-in way to configure timeouts for individual steps in Durable Functions. Steps can run up to the maximum Lambda function timeout, with automatic retry capabilities across multiple invocations.
Current Behavior:
- Each step can use up to the maximum Lambda function timeout
- If a step doesn't complete before timeout, a new invocation occurs with automatic retry
- Steps with retry configuration can span multiple invocations
Feature Request:
Add configurable timeouts at the step level to support:
- Maximum duration limits for individual steps
- Custom timeout configurations independent of Lambda function timeout
Possible Implementation
No response
Is this a breaking change?
No
Does this require an RFC?
No
Additional Context
No response