This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(83.2, 51%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ENN%3C/text%3E%3C/svg%3E)
I'm using triggered web job. After deploying the web job with a static configurable time its working, but I want to automate
the triggered job to any dynamic configurable time, so that it will be triggered based on that dynamic value.
For dynamic timer trigger I have prepared one method that will get value from DB and prepare and return cron expression and I have
used INameResolver to resolve name like %configurabletime% , but here back ground job is not triggering based on
the timer trigger value.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(32, 98%, 13%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMR%3C/text%3E%3C/svg%3E)
Hi,
Have you tried continuous web job?
https://learn.microsoft.com/en-us/azure/app-service/webjobs-create
No, I have tried with triggered web job only.
No, I mean type as continuous.
Yes, the type I have selected as 'triggered'
Hi,
you must have configured the scheule and the with the cron expression. Is it working fine when you pass the parameter through your code directly? I understand that you want to configure this dynamically, but before that please try through code just to check if that is working in that mode.
That is working fine when I pass the cron expression(eg: 0 0 * * * *) through the code, and if I prepare the cron expression in another method and passing like %configurabletime% then also that is working fine, and that configurable time value can change at any time in the UI, so If I update that value then web job is not firing with latest value, that is firing with the old value only.