Warning
You're browsing the documentation for an old version of Webiny. Consider upgrading your project to Webiny 5.41.x.
Use with caution!
This feature is experimental and is subject to change in future releases.
Can I use this?

This feature is available since Webiny v5.39.0.

What you’ll learn
- what to be careful about - limits of AWS Services

What to Be Careful About
anchor

Lambda Timeout
anchor

AWS Lambda can run up to 15 minutes. Webiny provides a mechanism for checking on how much time is there left before the Lambda times out, but it is up to the developer to use it. You can read about it here.

Step Function Timeout
anchor

AWS Step Function can live up to 1 year. This is the maximum time for the Step Function, set by AWS, and it cannot be increased.

Step Function Execution Limit
anchor

AWS Step Function has a hard limit of 25,000 state changes - executions. It cannot be increased.

Step Function State Change Limit
anchor

AWS Step Function does not provide a built-in mechanism to limit the number of state changes on each task run.

This means that a task can go into unwanted loop and execute up to 25,000 times, which is something that we want to avoid, or at least, control it.

What Webiny does to help with this is count the number of the Lambda handler executions, and if the number is greater than defined, it will end the task with an error.

Default limit: 500.

To change the limit, see maxIterations parameter when defining the Background Task.

Resumable Background Tasks
Currently, Background Tasks are not using the Task Token, so they are not resumable. We will be working on the solution for this in the future.