ERP Health Check Call is Taking More Than 7200 Seconds

Example

Timeout exception occurred, erp health check call is taking more than 7200 seconds.

Meaning

The health check ran for too long and timed out because Textura waited for a response from the ERP connection, but the response did not complete within the allowed time.

Possible Causes

Sage 300 or the related database is responding slowly.
The ERP server is overloaded or unavailable.
A network connection between Textura and the ERP environment is slow or unstable.
The integration process is stuck waiting for Sage 300, ODBC, or a backend component.
A local ERP prompt or system dialog may be blocking completion.

Recommended Resolution

Contact Textura Support, your ERP administrator, or your ERP consultants to review ERP server availability, network connectivity, and Sage 300 performance at the time of the timeout.

Next Topic: Connection Timed Out While Establishing DLL Connection / Check Pop Ups in Sage