What is system property "glide.export.ecc_response.timeout" and what is the optimal valueSummaryWe hear this question many times about what is the optimal value for system property glide.export.ecc_response.timeout. To better answer this question let's first understand what is the scope/purpose of this property. The scope of system property glide.export.ecc_response.timeout is limited to export set functionality when communicating with MID server. This property stores a numeric value in milliseconds demonstrating the number of seconds without a MID server connectivity before timing out the Export Set. When there is a connectivity issue between a ServiceNow instance and respective MID server due to whatever reason (most probably due to network congestion), this is when property comes into picture and ServiceNow instance wait for MID server response as per this property value. When there is no response received within defined time frame, the Export Set transaction got timed out with an error. Also please note, the minimum value for this property is 10. If it's set to a value below 10, we may see an error "glide.export.ecc_response.timeout value is too small, update to a value > 10 secs". Out of the box, the default value of this property is 300 secs and you can always increase is up to 600 or 900. But please bear in mind increasing this property value is a temporary and unfriendly sort of solution as it only helps to buy sometime to ServiceNow instance to wait for MID server response when MID server is not available due to whatever reason. Hence, there is no best optimal value for this property. The focus should be rather on restoring MID Server connectivity area (which is most probably a network issue at its core) and not on this system property value as there is no guarantee that the connection issue will be solved in 300 seconds or 900 seconds.