I've had an Azure Function working for like 3+ years. I've made all sorts of changes over the years, no triggering issues. I just updated one line and republished using Azure Function Core Tools (the same method I've always used to publish to Azure).
For some reason, the queues are just sitting in the Queue Storage, but they are not triggering the Function.
Done so far:
- Made one new change to the python code
#chunk = downloader.read(size=CHUNK_SIZE)
chunk = downloader.read(size=min(CHUNK_SIZE, end - offset + 1))
func azure functionapp publish <my-function-app-name>
- The
Remote build succeeded!
- Uploaded a file to Blob Storage (where I have an EventGrid subscription setup)
- This is the same thing that has worked for 3+ years
- I verified that
App Settings
have not changed at all (notice, I didn't use the--publish-local-settings
flag) - I restarted the Function App
- Published 2x, deployment center shows all good
- The function executed a couple times then quit
- Here are the queue's just sitting in the Queue Storage, not triggering the Function
- Can't figure out why the "Advanced Filters" are sometimes executing...
I'm at a loss here. Does anyone have a tried and true method for troubleshooting this issue?
Grrrr... was the
queueName
infunction.json
. I need a cleaner way to handle DEV/PROD environments. I had aprod
suffix though I was publishing todev
.