In the third part we look at how the orchestrator function triggers activity functions and handles their results

In the second part we take a look at what Durable Functions does under the hood when you tell it to start an orchestration

In the first part we will look at what happens during the startup process of an instance in Durable Functions

How to keep track of which parallel tasks have completed and make it visible in an orchestrator's custom status

Approaches for cleaning up execution history of completed Durable Functions instances

Deep dive into how Azure Durable Functions handle scaling as the amount of work changes