Azure function is not triggering after deployment or modification
Issue:
· Why does my azure
function sometimes stop being triggered?
· I just deployed
my function and it is not running or triggering.
· I changed something
to function.json but my function stopped triggering after that.
Solution:
This is very common
scenario and many people face this. There is no message on the portal which
helps us to identify the cause of this issue.
The primary
reason for this issue is related to 2 points,
· Deployment method
· Synchronization
For many deployments
methods synchronizations happen in backend automatically but for few deployments
methods it doesn’t happens as function runtime is not aware of these changes.
If you deploy
or change function app through following way then sync must be done manually,
· FTP
· WEBSITE_RUN_FROM_PACKAGE
· App Service
Editor
· KUDU
· Visual studio cloud
explorer.
· Update file in storage
directly.
You can use the following
options to sync your function manually,
· Option 1: Click
on the refresh button of your function app?
· Option 2: Go to
resource explorer of your function and search for the
o
Sync
API
o
PowerShell
sync command
# Action syncfunctiontriggers
Invoke-AzureRmResourceAction
-ResourceGroupName <RG name> -ResourceType Microsoft.Web/sites
-ResourceName <fuctionname> -Action syncfunctiontriggers -ApiVersion 2018-02-01 -Force
|
· Option 3:
Restart the function app which calls the Sync API internally.
Please
verify the deployment method and if this doesn’t solve the issue then reach out
to Team Azure.
References,
No comments:
Post a Comment