locked
Why is my reoccurring job failing every time? RRS feed

  • Question

  • I have a Console Application project that has been deployed as an Azure Web Job and is scheduled to run on a re-occurring basis (via classic Azure Portal) every 10 minutes with a running time of 6 to 7 minutes.

    The job results in a status of Failed every time citing it 'was aborted due to no output nor CPU activity for 121 seconds'. If I increase the WEBJOBS_IDLE_TIMEOUT value then the job will not be executed again due to the error 'Cannot start a new run since job is already running'.

    How can I get Azure WebJobs to realize that the job was executed successfully and run the next scheduled re-occurrence of this web job?

    Monday, January 4, 2016 8:41 AM