Azure Functions - Durable Functions cross contamination between function projects

[graemefoster]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

When running multiple function projects under Aspire (9.1.xxx as 9.3.xxx doesn't allow more than 1 function app to run due to existing issue)

I regularly see cross-contamination between storage accounts where the orchestration instances from 1 function app land in the storage account associated with another.

I will for example see the ...AgentHubHistory table populated in one storage account, but the ...AgentHubInstances table is empty.
I then see the instances pop up in a storage account related to one of the other function apps.

Makes it impossible to run multiple function apps reliably locally under Aspire.
Everything works fine when I run the function apps outside Aspire, either sharing one stg account (separate task hubs), or using multiple.

I noticed that Aspire doesn't run the function projects using "func", but uses "dotnet" directly. Unsure if related, but thought it worthwhile calling out.

This is in Rider.

Expected Behavior

Multiple Durable Function projects should be capable of running in Aspire and not affecting each other.

Steps To Reproduce

Create two Durable Function apps.
Pull them into Aspire.
Run them.

Exceptions (if any)

You see exceptions in the storage accounts about Orchestrations not existing in the projects.

.NET Version info

Running on dotnet 8 LTS.

Anything else?

No response

[graemefoster]

Adding some screenshots to try demonstrate what I see.
I have 3 durable function projects. Each creates its own storage:

I've just run a few orchestrations and suddenly I see this in the travel agent - note the tables for the Flight Company suddenly appeared: The business logic invoked a HTTP endpoint on the Flight Company function to crete an orchestration in the Flight Company

Things are all wired up correctly according to Aspire. I see the correct tables created in the Flght Companie's storage account when things start:

I originally had them all using 1 storage account and separate task hubs. But even in that scenario I got cross-contamination between the task hubs.

Again, no problems when I run them all outside of Aspire.

[graemefoster]

Closing - now getting the same behaviour outside of Aspire... So it's something with the Azure Functions host / the way it interacts with isolated Durable functions.

[graemefoster]

If anyone stumbles on this, the issue was down to me using this API:
builder.Services.AddDurableTaskClient(c => c.UseGrpc());

To inject a Durable Task Client. I suspect it doesn't always find the right GRPC port for the functions worker.