Timeout expired. Invoking an External System using Web Service

3 Years Ago
JorgeR
SCHEDULER AND UNDERLYING SERVICES

Summary

When your Bizagi application tries to connect to an External System using Web Service, a timeout error may be displayed.

Applies to

Bizagi 9.1.x, 10.x

Symptoms

When your Bizagi Application tries to connect using Web Services to get or send business data, a timeout error may be thrown. This error can generate delays and affect the performance of the Work Portal. The following is an example of the error displayed:

Date Time:
9/13/2012 11:53:56 AM
Source:
BizAgi
Message:: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding

Cause

This error is most likely displayed when the timeout parameters defined in Bizagi are not correctly specified.

Solution

You can set a timeout for each interface: that is, the time that the interface will wait for a response. When the Web Service is being called form an automatic task, you can define its timeout in the activity properties.

 

For a Web Service invoked form an asynchronous activity, the timeout is defined as the minimum time between the timeout property and the interface timeout (defined in Interfaces administration in system module).


Details

Last Modified:3 Years Ago
Last Modified By: JorgeR
Type: ERROR
Level: Beginner
Rated 4 stars based on 1 vote
Article has been viewed 5.4K times.

Options