Aria Automation Day2 Actions fail with error "Extensibility triggered task failed. Event ID: ...-...-...-...-... Failure: Timeout: due was '...' but expired
search cancel

Aria Automation Day2 Actions fail with error "Extensibility triggered task failed. Event ID: ...-...-...-...-... Failure: Timeout: due was '...' but expired

book

Article ID: 377420

calendar_today

Updated On:

Products

VMware Aria Suite

Issue/Introduction

Symptoms:

  • Several Day2 actions are failing with error "Extensibility triggered task failed. Event ID: ...-...-...-...-... Failure: Timeout: due was '...' but expired
  • The timeout value seen occurred in the past before the request was sent

 

Example Screenshot:

 

Environment

Aria Automation 8.17 & Later

Cause

The default project timeout value of 120 minutes is insufficient for completing certain Day-2 actions.

Resolution

 

Please configure a higher request timeout for the project associated with the impacted deployments.

The optimal timeout value may differ across environments, as it can be influenced by external factors such as network latency or the complexity of configured workflows.

If no custom value is set, the default request timeout of 2 hours will be applied.

Increase Deployment Timeout per Project:

  1. Login to Aria Automation (Assembler).

  2. Go to Infrastructure > Projects.

  3. Select the project you want to modify.

  4. Go to the Provisioning tab.

  5. Look for the setting "Request Timeout" (default is 120 minutes).

  6. Increase the value (e.g., '180m or 3h').

  7. Click Save.

Repeat this for each project where you want a longer deployment timeout.