Hello,
We have a web API that's timing out way too soon (about a minute) even though we set the executionTimeout in the web.config file to 360 seconds. We are wondering why this is.
My google research tells me that the executionTimeout will only apply if the debug attribute in the compilation tag is set to false. But we tried this and the timeout still only lasts about a minute.
I am also wondering if the executionTimeout applies to cases where the API is being blocked by a database call. That is to say, it's not so much the API itself which is taking more than a minute to respond to the request but a call that it makes to the database. I am testing the timeout under a condition where another process is accessing the database and blocking the API from getting access to the database. Thus, the API makes the call to the database and must wait for the first process to finish before it can return with the results of the query. This is what's causing the timeout. Would the executionTimeout attribute come into play in this case or should I be looking somewhere else to handle database call timeouts?
