Azure-docs: More information related to calling StartNewAsync while passing InstanceId

[harouny]

Its not exactly obvious the behavior of StartNewAsync when passing InstanceId while an existing orchestration with the same id already exists.

I was assuming the behavior might be just doing nothing since an orchestration with the same id already exists but seems like its doing some sort of restart (even if an instance is already in running state)

I can contribute to documentation once someone explains that behavior to me :)

Thanks

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 6c17b738-aa32-4cbb-3d82-bda2bc032487
• Version Independent ID: a34e246c-7c65-461f-4417-3c47eb4672e2
• Content: Manage instances in Durable Functions - Azure
• Content Source: articles/azure-functions/durable/durable-functions-instance-management.md
• Service: azure-functions
• GitHub Login: @cgillum
• Microsoft Alias: azfuncdf

[KetanChawda-MSFT]

@harouny Thank you for posting your question! We will review and update as appropriate.

@cgillum can you help here?

[cgillum]

@harouny you are right - it looks like we did not explain this in the official docs. There is a bit more detail in the API documentation here. Basically, if another orchestration with the same ID already exists, it will be silently overwritten with the new instance. It's not a behavior we like right now, but it's the way it works currently and will probably stay this way until we do a breaking 2.0 release. I'd be happy to review a docs PR if you want to open one. :)

[KetanChawda-MSFT]

@harouny We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.