1

I've been trying to deploy my Azure Durable HTTP Function app to my Azure resource group which I seem to have successfully done, to a degree at least.

When I go to the 'functions' tab enter image description here and click enter image description here to get the execution link, it kicks off the HTTP Trigger which calls the Durable Orchestrator which seems to 'schedule' the first Activity method in my Orchestrator, but not even the first line prints which is just a log. It printed ONE time which I found extremely strange as I had only restarted the Function App and ran it again.

There are so many ID's (processId, instanceId, operationId, etc) and so many other interfaces / diagnostic tools that I'm over-inundated with info and don't know how to make heads or tails of what's happening here.

I have App insights hooked up and the CPU will cap out at 100% as if the function app is running but nothing is happening.

Thank you for your help!

Improve this question
2
  • Share your actual function code. Commented Mar 6, 2022 at 19:13
  • Ok - the reason I didn’t provide it initially is because there’s too much PII so I was hoping it was a deployment configuration issue or something, but I will go through in the morning and clean out the details. Thank you Commented Mar 7, 2022 at 9:10

1 Answer 1

Reset to default
0

The solution to this issue was quite simple after all.

My environment variables in the local.settings.json weren't automatically migrated to the Azure environment after publishing as I assumed they would.

After manually entering them in the Azure 'configuration' blade, everything works fine.

Improve this answer
Sign up to request clarification or add additional context in comments.

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.