消耗计划在重新启动Function之前，函数不会触发blob存储事件 [英] Consumption plan Function not triggering off of blob storage event until I restart Function
问题描述
嗨大家好，
我在消费计划上部署了Azure功能应用程序。此应用程序具有blob存储触发器的功能。当文件上传到blob存储时，该函数应该执行。直到我手动
重新启动Function应用程序之后，该函数才会执行。这种情况发生在一段时间没有使用之后 - 例如，在没有使用的情况下过夜。一旦我们重新启动应用程序，函数将按预期触发。
I have an Azure Function application deployed on a consumption plan. This application has a function with a blob storage trigger. When a file is uploaded to blob storage the function is supposed to execute. The function is not executing until I manually restart the Function application, though. This happens after a period of no usage - over night without being used, for example. Once we restart the application the functions will trigger as expected.
最初，我使用专用虚拟机部署此应用程序，而不是消费计划，我不记得曾经有过这个在那里问题。当我切换到消费计划时，似乎已经开始出现这个问题了。
Originally, I had this application deployed using a dedicated virtual machine, instead of consumption plan, and I don't recall ever having this issue there. This issue seems to have began when I switched over to a consumption plan.
函数应用程序与blob存储事件的任何位置之间的连接引擎似乎都存在问题。来自。函数应用程序在它坐下并等待这些事件时不会生成任何日志或任何内容 - 我看不到
错误或任何内容。一旦我重新启动应用程序，它就会获取事件并按预期触发该功能。
It seems to be an issue with the under-the-hood connection between the Functions application and wherever the blob storage events are received from. The Function application generates no logs or anything while it sits and waits for these events - I see no errors or anything. Once I restart the application, it picks up the events and triggers the function as expected.
任何想法？
推荐答案
看起来像是同步触发器问题但目前还不确定。
您是否可以尝试在门户中单击功能的刷新按钮？我不确定这个问题到底是什么，但我想知道是否能修复它。
最常见的问题导致Azure功能无法触发的是，某些部署或IDE不会使用中央侦听器
触发消费计划上的同步 。这在GitHub线程中有解释。
The most common issue for causing Azure Functions not to trigger is that some deployment or IDEs do not trigger a synchronization on a consumption plan with the central listener. This is explained in this GitHub thread.
https://github.com/Azure/Azure-Functions/issues/210
这篇关于消耗计划在重新启动Function之前，函数不会触发blob存储事件的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
