We have an Azure web site with a daily scheduled job. In our case, the scheduled job runs a stored procedure that takes about 10 minutes so there is no local processing. Our web job is terminating after about 4 minutes with this error.
Command 'cmd /c ...' aborted due to no output and CPU activity for 121 seconds.
You may increase SCM_COMMAND_IDLE_TIMEOUT setting to solve the issue.
We've tried adding the following app settings to the web job's app.config file:
<appSettings>
<add key="SCM_COMMAND_IDLE_TIMEOUT" value="100000" />
<add key="WEBJOBS_IDLE_TIMEOUT" value="100000" />
</appSettings>
Those files are referenced in this document https://github.com/projectkudu/kudu/wiki/Web-jobs but they don't seem to have any effect. (still timing out after adding the settings to the app.config file)
Are we adding the configuration settings to the right place?
Thanks for the help.
You need to set SCM_COMMAND_IDLE_TIMEOUT from the portal to your desired timeout value in seconds. For example, set it to 3600 for a one hour timeout.
Go to your website's config section, find the app settings section, and add the setting.
Login to Microsoft Azure portal
Go to App Services,
Select your website
Go to settings --> Application settings tab
Create a key “WEBJOBS_IDLE_TIMEOUT” under App settings section
Save
来源：https://stackoverflow.com/questions/26596968/azure-webjob-timeout-configuration-settings