Azure Functions with Durable Task Framework: Task Hub Name Conflict scenarios in Production
I'm working with an scenario with Azure Durable Functions when deploying to my production environment. I have several function apps that use the Durable Task Framework, and they all seem to be attempting to use the same Task Hub name: 'MyDurableTaskHub'. This is causing a conflict, and I receive the following behavior message: ``` The Task Hub 'MyDurableTaskHub' already exists in the storage account 'myaccountstrg' and want to be created again. ``` In my development environment, each function app is configured with a unique Task Hub name, which works fine. Here's the setup I have for the Durable Functions in my production deployment: ```csharp public static class MyDurableFunction { [FunctionName("MyDurableFunction")] public static async Task Run([OrchestrationTrigger] IDurableOrchestrationContext context) { // Orchestration logic here } } ``` In my `local.settings.json`, I have: ```json { "AzureWebJobsStorage": "DefaultEndpointsProtocol=https;AccountName=myaccountstrg;AccountKey=mykey;EndpointSuffix=core.windows.net", "DurableTaskHubName": "MyDurableTaskHub" } ``` And in my production configuration (via Azure Portal), I've set the same connection string. I’ve tried modifying the Task Hub name directly in the Azure Portal configuration on each function app to something unique (like 'MyDurableTaskHub1'), but I still see the same behavior. I also verified that there are no lingering instances of this hub left over from previous deployments. Is there a specific way I should be handling Task Hub names when deploying multiple Azure Function apps that utilize Durable Functions? Any best practices or configurations I might be missing? Thanks for your help! I'm on Ubuntu 22.04 using the latest version of C#. Thanks for taking the time to read this!