[Question] (C# compiled functions) Some functions when deployed to azure seem to need the webapp restarted before picking up changes
- Dominant language
- PowerShell
- Stars
- 1.1k
- Forks
- 215
- Avg merge
- 4h 2m
- Merged PRs (30d)
- 1
Description
Hi, more a question as I haven't found anything obvious in the docs and I see this happen every now and then...
(This is a C# Compiled function app using the preview VS tooling. Being deployed by a VSTS deployment agent using the webapp package upload. Running on a Consumption Plan).
Sometimes, more noticeably when adding a new function, it may not be accessible after the deployment has finished. If I navigate to the functionApp on azure, I see the function in the list. When I click on the name I get an error that includes "The function type name 'XYZ' is invalid.", but still lists the json describing the function, etc.
If I restart the functionApp and go back to it - all good.
Q) Is there a delay between the deployment and the running function detecting that the files have actually changed?
Has anyone else seen this before?
Thanks,
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.