Error: Loading Prompts: Request timed out (180000) - Automic Web Interface
search cancel

Error: Loading Prompts: Request timed out (180000) - Automic Web Interface

book

Article ID: 445887

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

When opening an Automic BusinessObjects (BOBJ) job in the Automic Web Interface (AWI), the prompts fail to load. The interface returns a timeout error after exactly 180,000 milliseconds (3 minutes). This occurs when the integration is waiting for a response from the SAP BusinessObjects server.

 

Symptoms

Users see the following error message in the AWI UI: Error Loading Prompts: Request timed out (180000)

Environment

  • Automic Web Interface (AWI)
  • Automic Automation Engine
  • SAP BusinessObjects Integration

Cause

The default timeout for asynchronous loading in the Automic Web Interface is set to 3 minutes (180000ms). If the SAP BusinessObjects server takes longer than this to return the prompt metadata or list of values, the AWI terminates the request.

Resolution

To resolve this issue, work with the SAP team to determine an appropriate timeout value. It is possible that there is an underlying performance or configuration issue in SAP that needs to be addressed. The SAP team should advise on what an acceptable response time is for your environment and determine when they should be notified to investigate further delays.

 

Workaround

To workaround this issue, increase the asynchronous loading timeout in the AWI configuration.

  1. Log in to the server where the Automic Web Interface (AWI) is installed.
  2. Navigate to the AWI configuration directory (typically ####/apache-tomcat/webapps/awi/config/).
  3. Open the configuration.properties file in a text editor.
  4. Locate or add the parameters below: (Note: This example increases the timeout to 30 minutes. Adjust this value based on your environment's requirements.)

    asyncLoadingTimeoutMilliseconds=1800000
    automationEngineTimeoutMilliseconds=1800000
    xRequestExecutorTimeoutMilliseconds=1800000

  5. Save the file.
  6. A restart of the Tomcat application server should not be necessary for the changes to take effect.

⚠️ Review this change with your administrator. Extremely high timeout values may mask underlying performance issues on the SAP BusinessObjects server.

If the issue persists, verify with your SAP BusinessObjects team that the integration user has the necessary permissions to fetch the List of Values (LOV) and that the SAP HANA variables are performing optimally.