Time limit on Azure Webjobs triggered by Queue -

are there time limits on queue triggered function inside azure web job. function takes 20-30 mins since needs go on lot of records in db. function status in end never finished. put in settings.job file { "stopping_wait_time": 1800 } - no effect. within 5 minutes or status set never finished. searched , yes found ppl asking similar questions - no definitive answers. found exceptions in logs , exceptions seemed generated azure storage. searched , found there issues logging, commented out logging code within function - still no go. found 1 question mentioned connection strings - have these; azurewebjobsstorage, azurewebjobsdashboard, azurejobsruntime, azurejobsdata - pointing same storage account - still no go.

i tried debug, , see timeout occurs , seems happening before function hit,

output below;

a first chance exception of type 'system.net.webexception' occurred in system.dll first chance exception of type 'system.net.webexception' occurred in system.dll first chance exception of type 'system.timeoutexception' occurred in microsoft.windowsazure.storage.dll first chance exception of type 'microsoft.windowsazure.storage.storageexception' occurred in microsoft.windowsazure.storage.dll first chance exception of type 'microsoft.windowsazure.storage.storageexception' occurred in microsoft.windowsazure.storage.dll first chance exception of type 'microsoft.windowsazure.storage.storageexception' occurred in mscorlib.dll first chance exception of type 'microsoft.windowsazure.storage.storageexception' occurred in mscorlib.dll first chance exception of type 'microsoft.windowsazure.storage.storageexception' occurred in microsoft.azure.webjobs.host.dll system.transactions critical: 0 : <tracerecord xmlns="http://schemas.microsoft.com/2004/10/e2etraceevent/tracerecord" severity="critical"><traceidentifier>http://msdn.microsoft.com/tracecodes/system/activitytracing/2004/07/reliability/exception/unhandled</traceidentifier><description>unhandled exception</description><appdomain>pncprocessor.exe</appdomain><exception><exceptiontype>microsoft.windowsazure.storage.storageexception, microsoft.windowsazure.storage, version=4.3.0.0, culture=neutral, publickeytoken=31bf3856ad364e35</exceptiontype><message>the client not finish operation within specified timeout.</message><stacktrace>   @ microsoft.windowsazure.storage.core.executor.executor.endexecuteasync[t](iasyncresult result) @ microsoft.windowsazure.storage.queue.cloudqueue.endexists(iasyncresult asyncresult) @ microsoft.windowsazure.storage.core.util.asyncextensions.&amp;lt;&amp;gt;c__displayclass1`1.&amp;lt;createcallback&amp;gt;b__0(iasyncresult ar) --- end of stack trace previous location exception thrown --- @ system.runtime.compilerservices.taskawaiter.throwfornonsuccess(task task) @ system.runtime.compilerservices.taskawaiter.handlenonsuccessanddebuggernotification(task task) @ microsoft.azure.webjobs.host.queues.listeners.queuelistener.&amp;lt;executeasync&amp;gt;d__4.movenext() --- end of stack trace previous location exception thrown --- @ system.runtime.compilerservices.taskawaiter.throwfornonsuccess(task task) @ system.runtime.compilerservices.taskawaiter.handlenonsuccessanddebuggernotification(task task) @ microsoft.azure.webjobs.host.timers.taskseriestimer.&amp;lt;runasync&amp;gt;d__d.movenext() --- end of stack trace previous location exception thrown --- @ microsoft.azure.webjobs.host.timers.backgroundexceptiondispatcher.&amp;lt;&amp;gt;c__displayclass1.&amp;lt;throw&amp;gt;b__0() @ system.threading.threadhelper.threadstart_context(object state) @ system.threading.executioncontext.runinternal(executioncontext executioncontext, contextcallback callback, object state, boolean preservesyncctx) @ system.threading.executioncontext.run(executioncontext executioncontext, contextcallback callback, object state, boolean preservesyncctx) @ system.threading.executioncontext.run(executioncontext executioncontext, contextcallback callback, object state) @ system.threading.threadhelper.threadstart()</stacktrace><exceptionstring>microsoft.windowsazure.storage.storageexception: client not finish operation within specified timeout. ---&amp;gt; system.timeoutexception: client not finish operation within specified timeout. --- end of inner exception stack trace --- @ microsoft.windowsazure.storage.core.executor.executor.endexecuteasync[t](iasyncresult result) @ microsoft.windowsazure.storage.queue.cloudqueue.endexists(iasyncresult asyncresult) @ microsoft.windowsazure.storage.core.util.asyncextensions.&amp;lt;&amp;gt;c__displayclass1`1.&amp;lt;createcallback&amp;gt;b__0(iasyncresult ar) --- end of stack trace previous location exception thrown --- @ system.runtime.compilerservices.taskawaiter.throwfornonsuccess(task task) @ system.runtime.compilerservices.taskawaiter.handlenonsuccessanddebuggernotification(task task) @ microsoft.azure.webjobs.host.queues.listeners.queuelistener.&amp;lt;executeasync&amp;gt;d__4.movenext() --- end of stack trace previous location exception thrown --- @ system.runtime.compilerservices.taskawaiter.throwfornonsuccess(task task) @ system.runtime.compilerservices.taskawaiter.handlenonsuccessanddebuggernotification(task task) @ microsoft.azure.webjobs.host.timers.taskseriestimer.&amp;lt;runasync&amp;gt;d__d.movenext() --- end of stack trace previous location exception thrown --- @ microsoft.azure.webjobs.host.timers.backgroundexceptiondispatcher.&amp;lt;&amp;gt;c__displayclass1.&amp;lt;throw&amp;gt;b__0() @ system.threading.threadhelper.threadstart_context(object state) @ system.threading.executioncontext.runinternal(executioncontext executioncontext, contextcallback callback, object state, boolean preservesyncctx) @ system.threading.executioncontext.run(executioncontext executioncontext, contextcallback callback, object state, boolean preservesyncctx) @ system.threading.executioncontext.run(executioncontext executioncontext, contextcallback callback, object state) @ system.threading.threadhelper.threadstart() request information requestid: requestdate: statusmessage: </exceptionstring><innerexception><exceptiontype>system.timeoutexception, mscorlib, version=4.0.0.0, culture=neutral, publickeytoken=b77a5c561934e089</exceptiontype><message>the client not finish operation within specified timeout.</message><stacktrace>   @ microsoft.azure.webjobs.host.timers.backgroundexceptiondispatcher.&amp;lt;&amp;gt;c__displayclass1.&amp;lt;throw&amp;gt;b__0() @ system.threading.threadhelper.threadstart_context(object state) @ system.threading.executioncontext.runinternal(executioncontext executioncontext, contextcallback callback, object state, boolean preservesyncctx) @ system.threading.executioncontext.run(executioncontext executioncontext, contextcallback callback, object state, boolean preservesyncctx) @ system.threading.executioncontext.run(executioncontext executioncontext, contextcallback callback, object state) @ system.threading.threadhelper.threadstart() 

system.timeoutexception: client not finish operation within specified timeout.

i using s1 web app , standard-grs storage account this.

so questions are;
1. there time limitations on time queue triggered function takes?
2. if there time limitations there way override those?
3. have use queue triggered function since need pass parameters function - passed scheduled web job. can make on-demand webjob , pass parameters on command line - there way call on-demand webjob scheduled webjob?

thanks help!

no there no limit on execution time of queue triggered job functions. there few things have ensure set jobhost continues run. when using azure webjobs sdk need deploy jobhost console exe continuously running webjob, , enable always on. both of described in detail on this documentation page under "create continuously running webjob" section.

see "notes" section of page relevant details on timeout limits when running in free tier (20 minute timeout), can removed moving basic or standard tier.