scheduleNewOrchestrationInstance function doesn't throw an error if instanceId already exists about durabletask-java HOT 8 CLOSED

I just realized that we already have a fix in PR for this issue: Azure/azure-functions-durable-extension#2489.

from durabletask-java.

Resolved by Azure/azure-functions-durable-extension#2489 (pending release)

from durabletask-java.

Seems to be a bug, need investigation.

from durabletask-java.

@kaibocai Any updates on this?

from durabletask-java.

Hi @kanupriya15025 , sorry that the team is currently focusing on other priority tasks. We will put this on our working list once the team has some spare capacity. Thanks for your understanding.

from durabletask-java.

I took a closer look at this with help from @kamperiadis. The problem is in the Durable extension running in the Functions host. There is a bug where code paths for out-of-proc languages are not correctly checking for existing instances. My recommendation is that we make a change here to pass a list of de-dupe status values to ensure that we throw an exception for existing/running instances.

Note that this will be a breaking change that needs to be called out in the release notes.

from durabletask-java.

@jviau Is this released with v1.1.1? Because it still doesn't give me an error with same instanceId.

from durabletask-java.

@jviau Is this released with v1.1.1? Because it still doesn't give me an error with same instanceId.

@kanupriya15025 , the issue is fixed in durable function extension, the repo is at https://github.com/Azure/azure-functions-durable-extension, the release that contains the fix is https://github.com/Azure/azure-functions-durable-extension/releases/tag/v2.9.6.

In this case you need to manually update the durable function extension on your local, where you can find steps at https://learn.microsoft.com/en-us/azure/azure-functions/durable/durable-functions-extension-upgrade#manually-upgrade-the-durable-functions-extension

from durabletask-java.