Harshveer Singh (Inactive) added a comment - 18/May/20 12:51 AM API Timeouts are happening when worker process is initializing for first time after being terminated. We need to take 2 steps to resolve this:   After app pool recycle we need to warmup the API servers. If we don’t do this then very first request to API after recycle generally timeouts causing error in other applications integrated with DMS. You can use below line in your script to make an API call each server directly(not to load balancer serve using URL) after recycling:     Stage:         powershell.exe -noprofile -command "Invoke-WebRequest -Uri http://172.16.196.4:88/api/user/GetSecurityQuestions "         powershell.exe -noprofile -command "Invoke-WebRequest -Uri http://172.16.196.5:88/api/user/GetSecurityQuestions "     Prod:         powershell.exe -noprofile -command "Invoke-WebRequest -Uri http://172.16.196.4:89/api/user/GetSecurityQuestions "         powershell.exe -noprofile -command "Invoke-WebRequest -Uri http://172.16.196.5:89/api/user/GetSecurityQuestions "                 Port binding which I have provided in above script might not exist, so please validate that some other binding except 443 exists and use that. Also we need to remove Idle time-out from DMS App pool setting(set it to 0) so that worker process doesn’t terminate after inactivity.   Ashwin Wankhede Ashish Durani Samir