Events and subscriptions that run longer than 30 minutes can cause requests to fail
search cancel

Events and subscriptions that run longer than 30 minutes can cause requests to fail

book

Article ID: 396698

calendar_today

Updated On:

Products

VMware Aria Suite

Issue/Introduction

When performing any actions that include subscription workflows that last longer than 30 minutes may cause the action to fail.

Example error string:

SubscriberID: vro-gateway-########, RunnableID: ######-#####-####-####-########## and SubscriptionID: sub_########## failed with the following error: No reply from blocking subscription Check vRA Machine Expiration(id=sub_##########)

Environment

VMware Aria Automation 8.x

Cause

Default timeout for workflows in projects are 30 minutes unless modified in Project Settings.

Resolution

  1. Modify your Request Timeout value in the Infrastructure > Administration > Projects > <your project>.
  2. Under the Provisioning tab you will find a section called Request Timeout.
  3. Modify to an appropriate timeout that will allow your workflows to complete. 

Example with a 2 hour timeout: