Your Durable Function runs many times

Frequently asked questions

Why does a Durable Functions orchestrator run from the top every time?

The orchestrator replays its entire function body from line one on every checkpoint, but activities that already completed answer instantly from the recorded event history instead of running again — that's how it resumes exactly where it left off without keeping the process alive between awaits.

Why do DateTime.Now and Guid.NewGuid break a Durable Function?

Replay re-executes the same code path multiple times, so any non-deterministic call would return a different value on each replay and desynchronize the orchestrator from its own history. Use the context's deterministic equivalents instead.

Read deeper on Azure

Twenty seconds gets the shape of an idea across. These go into how it behaves in production.

• How Azure Protects a Mobile App: The Full Request Flow, Layer by Layer

  Front Door, your API, Microsoft Entra ID, authorization and a private database — the five layers that stand between a mobile app and its data on Azure.

• Your Mobile App Is Leaking Its API Key — and Obfuscation Will Not Save It

  An APK or IPA is a zip file. Anything hardcoded inside it, including your API key, is already public — and here is how to get it off the phone for good.

• What Is Microsoft Foundry (Azure AI Foundry)? The Services, and When You Actually Need Them

  A plain tour of Microsoft Foundry for developers: the resource, projects, models, agents, tools, and when Azure OpenAI on its own is enough.