updating timer trigger did not properly reschedule the job
See original GitHub issueHi,
I have a job that runs weekly and processes payments. I typically have this job run on Tuesday at 9am UTC, but I had some fixes that I needed to push out and decided to delay it by a day. To do this, I used the debug console in Azure portal to open the function.json
file in the online editor and changed Tue
to Wed
. Here’s the resulting file:
{
"bindings": [
{
"type": "timerTrigger",
"name": "timerInfo",
"direction": "in",
"schedule": "0 0 9 * * Wed",
"runOnStartup": false
}
]
}
To my surprise, I woke up this morning to find that the job had run.
To further complicate things, I’m seeing the following output from the functions dashboard:
Related information
Provide any related information
- Running Node.js
- Functions runtime v1.0.10690
Update
I just did a test to see if the job “appears” to reload when changing the file and according to the logs, I do see that the functions runtime stopped and then restarted. I’m assuming that this is the job reloading.
Is there something with the way these timer triggers are scheduled that would have caused the previously scheduled job to remain even though I had updated function.json
to a new schedule?
Thanks again
Issue Analytics
- State:
- Created 7 years ago
- Comments:14 (6 by maintainers)
Top GitHub Comments
I’ve just committed a change for your initial issue (the timer firing when you changed the schedule): https://github.com/Azure/azure-webjobs-sdk-extensions/pull/195.
I’m going to close this issue – but if you’re able to find any more logs that indicate what may have happened with the staging/prod issues, please open a new issue and we’ll tackle it there. My current theory:
@brettsam sorry I never replied to this. I appreciate you submitting the fix.
A quick question: if I manually run the job, will it affect the scheduling of future jobs? I’m asking because our job didn’t fully complete when it ran on its normal schedule last night. It was an error in our code, but I need to run it again. However, I’m a bit gun shy to run it manually as I’m afraid of affecting the future schedule.
Thanks! James