Database Deadlock or Temporary Transaction Conflict

Meaning

The ERP database detected competing activity and ended the health-check request to let other database work continue.

Possible Causes

Several processes were accessing the same database resources.
Reporting, maintenance, or batch processing caused a temporary conflict.
The database was under heavy load.
A long-running operation held a required resource.

Recommended Resolution

Wait for Textura to retry the connection automatically.

If the error recurs, ask your database administrator to review locking and deadlocks around the recorded failure time. Contact Textura Support if needed.

Next Topic: Certificate or Trust Failure