Timer函数在调用另一个http函数之前不会触发 [英] Timer Function not firing until another http function is called

查看:87
本文介绍了Timer函数在调用另一个http函数之前不会触发的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我有一系列功能设置,其中很多是简单的http功能,其中2个是定时器


定时器没有按计划运行,而只是醒来当其中一个http函数被调用时


我试过多次点击刷新按钮并且似乎没有任何影响


好奇部分是我有2个具有相同功能的其他组(标记为Dev& QA),完全相同的设置,我可以看到它们已按计划运行而没有问题


详细信息:


1。消费计划


2。从DevOps部署 - 并已使用Web Deploy选项检查发布


3。 v1运行时


4。尚未设置时区属性


5。 CRON设置为 "0 30 23 * * 0"并希望它在UTC时间晚上11:30运行(美国东部时间为-5小时)


第二个计时器设置为 "0 20 8 1-7 * 1" ;并期待周一上午8:20


6。使用Azure日志作为它们未按计划运行的证据,日期/时间永远不会正确(尽管开发和QA组始终完美运行),并且还与http触发器日志的执行时间相匹配看到
,计时器在被调用的同时运行。 此外,首次发现问题是由于数据不正确而发现定时器没有以正确的顺序运行(周日显然应该在周一之前运行,但是b $ b反转发生在周一完成的情况下)第一个)


7。调用ID -  


2019-04-15 11:27:00.581

函数已启动( Id = 6727b340-bd82-45cf-9ba4-7e9822dc857c)
$

解决方案

您能否确认已启用Always On。默认情况下,它在应用服务计划中的功能应用上启用,但最好仔细检查。


另外正如您已经提到的那样,多次单击刷新按钮没有任何区别,但只是为了排除同步问题,您可以尝试
明确同步触发器  通过PowerShell
并查看是否有任何区别。




I have a collection of functions setup, many of them are simple http functions, 2 of them are timers

The timers have not been running on schedule, instead only waking up when one of the http functions get called

I have tried clicking the refresh button multiple times and hasn't seemed to have any impact

Curious part is I have 2 other groups of the same functions (labelled as Dev & QA), exact same setup as far as I can see and they have been running on schedule without issues

Details:

1. Consumption Plan

2. Deploying from DevOps - and have checked the Publish using Web Deploy option

3. v1 runtime

4. Have not set the timezone property

5. CRON set to "0 30 23 * * 0" and expecting it to run Sunday evenings at 11:30pm UTC (-5 hours for EST which I am in)

Second timer is set to "0 20 8 1-7 * 1" and expecting Mondays at 8:20am

6. Using the Azure logs as evidence that they are not running on schedule, the dates/times are never correct (though the Dev & QA groups have always run perfectly), and also matching up with the execution times from the logs of http triggers can see that the timers ran at the same time those were called.  Also, this was first found when an issue was raised with data being incorrect and was found that the timers didn't run in the correct order (Sunday obviously should have ran before the Monday, but the reverse happened where Monday's completed first)

7. Invocation id - 

2019-04-15 11:27:00.581
Function started (Id=6727b340-bd82-45cf-9ba4-7e9822dc857c)

解决方案

Could you confirm that Always On is enabled. It is enabled by default on Function Apps in App service plan, but it's good to double check.

Also as you have already mentioned that clicking the refresh button multiple times does not make any difference but just to rule out the sync issue could you try explicitly sync the triggers via PowerShell and see if that make any difference.


这篇关于Timer函数在调用另一个http函数之前不会触发的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆