Feature update: Action timeout setting in YAML configuration

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 Action tab:

Image loading...Action timeout location

Hint
If 90 minutes is not enough for your workflow, please contact support@buddy.works for a custom limit.

YAML configuration

Previously, the feature was reserved for pipelines configured via the GUI. With today's update, you can configure it in YAML files using the timeout parameter.

Hint
If the parameter is not set, it will assume the default 90-minute limit.

Image loading...Example YAML configuration

Danger
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. - KUBERNETES_APPLY – timeout_arg - CLOUD_FRONT – wait_for_completed - MONITOR – wait_if_grey
Jarek Dylewski

Jarek Dylewski

Customer Support

A journalist and an SEO specialist trying to find himself in the unforgiving world of coders. Gamer, a non-fiction literature fan and obsessive carnivore. Jarek uses his talents to convert the programming lingo into a cohesive and approachable narration.

Previous pageNew feature: Download files from remote server to filesystemNext pageDelegate permissions with AWS roles
Nov 14, 2019
Share