azure-functions-durable-extension: .StartNewAsync() and .RestartAsync() fail, when running locally and TaskHubName='TestHubName'

This is a follow-up on #1592. It turned out, that, when running outside Azure, DurableFunctionsMonitor fails to .RestartAsync() and/or .StartNewAsync(), if the Task Hub it is attached to is named ‘TestHubName’. With other Task Hubs it works fine. It also works fine (no matter what Task Hub is called) in Azure.

I believe it is due to this logic here, that turns on/off orchestration name validation.

Can we think of a better way to invoke that logic?

FYI, DfMon’s code, that makes the call, is here.

Expected behavior

Both .StartNewAsync() and .RestartAsync() succeed.

Actual behavior

System.Private.CoreLib: Exception while executing function: DfmPostOrchestrationFunction. Microsoft.Azure.WebJobs.Extensions.DurableTask: The function 'MapReduceOrchestrator' doesn't exist, is disabled, or is not an orchestrator function. 
Additional info: No orchestrator functions are currently registered!.

is thrown, when Task Hub is named ‘TestHubName’.

App Details

Durable Functions extension version (e.g. v1.8.3): 2.4.3
Azure Functions runtime version (1.0 or 2.0): 3.0
Programming language used: C#

About this issue

Original URL
State: open
Created 3 years ago
Comments: 16 (6 by maintainers)

Most upvoted comments

@davidmrdavid , this behavior is still the same, even with latest Microsoft.Azure.WebJobs.Extensions.DurableTask v2.6.1.

To reproduce, create a Function project, use “TestHubName” as a Task Hub name, get a default instance of DurableClient and call its .StartNewAsync() method with random parameters. Run all of this locally (not in Azure)

scale-tone on Apr 7, 2022