Summary

Bizagi provides access to the processes functionality and to the business information underlying in your data model, by featuring a powerful service-oriented API which is ready-for-use in every Bizagi project.

Bizagi API features a SOAP-compliant, comprehensive set of web services with convenient and easy-to-use methods.

When you try to invoke any of the methods provided by Bizagi and the method takes a long time (more than 110 seconds) ASP.NET will shut down the request and display the message shown in the title.

Applies to

Bizagi 10.x .NET

Symptoms

When invoking any method from Bizagi SOA, the message response will display the following error:

Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding

Cause

This issue is presented when the invocation exceeds the default timeout period for a request (110 seconds) and ASP.NET shuts it down. This value was chosen by Bizagi in order to protect the server from waiting for a response for very long periods of time.

Solution

It’s not common that the methods exposed by Bizagi SOA takes so long in the execution; in this case, it’s strongly recommended to analyze why the invocation takes so long to retrieve a response. To do this, review the input parameters for the methods and perform a full trace of the issue.
If after a thorough review, it is necessary you increase the execution timeout, perform the following steps:

1. Open the web.config file (located in C:\Bizagi\Projects\[ProjectName]\WebApplication) using the text editor of your choice.

2. Within <system.web> section, set/update the value for executionTimeout parameter of the httpRuntime tag:

<httpRuntime executionTimeout = "200" />

The value presented above indicates the number of seconds of the request before ASP.NET shuts it down. It may be increased or decreased according to your business needs.