Commerce Job SQL Timeout Configuration

  • Updated
Description

A commerce job like Maintain Database Indexes can be very expensive in terms of SQL resources and in some cases can timeout with an error like this.

 

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

 

Steps

In .NET Core apps, it may help to increase the timeout in the appsettings.*.json file. The following is six minutes (default is 30 seconds). 

"Commerce": { 
"DataOptions": { 
"DataBaseIndicesJobCommandTimeOut": 360,

source: Option configuration classes (optimizely.com)


In CMS 11, utilize this setting. 
episerver::DataBaseIndicesJobCommandTimeOut


As with most SQL timeouts, use your discretion when setting this and only run the job during slow periods. 


If it still times out, contact support to rebuild the indexes manually.