A couple of weeks ago we released an update allowing users to manually set the timeout for individual actions. At the same time, the previous limit of 90 minutes (5400 seconds) remains the maximum execution time that can be set in an action. The only exception are notifications which are sent instantly. The feature is available in the
If 90 minutes is not enough for your workflow, please contact firstname.lastname@example.org for a custom limit.
Previously, the feature was reserved for pipelines configured via the GUI. With today's update, you can configure it in YAML files using the
If the parameter is not set, it will assume the default 90-minute limit.
If you are using YAML with the following actions:
- K8s Apply
- Cloudfront invalidation
- Elastic Beanstalk Monitoring
you need to change the parameters below to
timeout as they are deprecated and will no longer be supported in 2020.