Durable Task Scheduler emulator Task Hub dashboard URL uses incorrect default route

Open Beginner friendly
#20,173 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
84/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
azure, csharp
Domain
cloud, tooling

Research direction

Start in src/Aspire.Hosting.Azure.Functions/DurableTask/DurableTaskResourceExtensions.cs, at AddTaskHub's OnResourceReady callback, and inspect how the dashboard URL is assembled. Verify the generated link uses the local emulator scheduler route, preserves the task hub name, and ends at the orchestrations path.

Written by the indexing model from the issue text.

Description

area-integrations triage:bot-seen
Is there an existing issue for this?
  • I have searched the existing issues
Describe the bug

When using the Durable Task Scheduler emulator through Aspire.Hosting.Azure.Functions, the generated Task Hub Dashboard URL uses a hard-coded default scheduler route instead of the actual local emulator route.

Aspire's DurableTaskResourceExtensions.AddTaskHub currently constructs the dashboard URL as:

$"{r.Parent.EmulatorDashboardEndpoint}/subscriptions/default/schedulers/default/taskhubs/{r.TaskHubName}"

The running emulator is exposed through the local emulator route, so the generated link does not identify the actual scheduler resource.

Expected Behavior

The generated local Task Hub Dashboard URL should target the emulator identity and orchestration route:

http://localhost:<port>/subscriptions/local/schedulers/emulator/taskhubs/<TASK_HUB_NAME>/orchestrations

The task hub name should remain dynamic, while the scheduler route should match the actual Aspire emulator proxy route.

Steps To Reproduce
  1. Create an Aspire AppHost using Aspire.Hosting.Azure.Functions 13.5.4.
  2. Add a Durable Task Scheduler emulator and task hub:
var scheduler = builder.AddDurableTaskScheduler("scheduler")
    .RunAsEmulator();

var taskHub = scheduler.AddTaskHub("taskhub")
    .WithTaskHubName("ZeusOrchestrationHub");
  1. Run the Aspire application.
  2. Open the Task Hub Dashboard URL shown by Aspire.

Actual URL:

http://localhost:<port>/subscriptions/default/schedulers/default/taskhubs/ZeusOrchestrationHub

The actual emulator route is:

http://localhost:<port>/subscriptions/local/schedulers/emulator/taskhubs/ZeusOrchestrationHub/orchestrations

A local workaround is to add a custom URL with the actual emulator route.

Exceptions (if any)

No exception is thrown. The issue is that the generated dashboard link is incorrect or non-functional.

Aspire doctor output
Aspire Environment Check
========================

Aspire
  ✅ Aspire CLI version 13.5.4 (channel: stable)
  ✅ Developer Control Plane (DCP) connection health checks succeeded

AppHost
  ✅ AppHost version 13.5.4 (Zeus.AppHost\Zeus.AppHost.csproj)

.NET SDK
  ✅ .NET 10.0.401 installed (x64)

Container Runtime
  ✅ Docker v29.8.0: running (auto-detected (default)) ← active

Environment
  ✅ Operating system: Windows 10.0.26200.0
  ✅ HTTPS development certificate is trusted

Development Tools
  ⚠️ VS Code is installed, but the Aspire extension is not installed
       Install the Aspire extension from the VS Code Marketplace for an integrated Aspire experience.
       See: https://aka.ms/aspire/vscode-extension

Summary: 7 passed, 1 warnings, 0 failed
For detailed prerequisites: https://aka.ms/aspire-prerequisites

Aspire CLI Installations
========================

╭──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┬─────────────────────────────────────────────────┬─────────┬───────────┬─────────────╮
│ Path                                                                                                                                         │ Version                                         │ Channel │ Route     │ PATH status │
├──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┼─────────────────────────────────────────────────┼─────────┼───────────┼─────────────┤
│ C:\Users\andrew.flatters\AppData\Local\Microsoft\WinGet\Packages\Microsoft.Aspire_Microsoft.Winget.Source_8wekyb3d8bbwe\aspire.exe (current) │ 13.5.4+9c1b401dd67746739044f68959cbf4d3d7af93a6 │ stable  │ (unknown) │ active      │
Anything else?

Environment:

  • Aspire.Hosting.Azure.Functions 13.5.4
  • .NET SDK 10.0.401
  • Windows
  • Azure Functions isolated worker
  • Durable Task Scheduler emulator

Impact:
The Aspire dashboard exposes a misleading or non-functional Task Hub Dashboard link for local DTS emulator resources. The emulator dashboard itself is accessible, and the consuming AppHost can work around this with:

taskHub.WithUrl(
    "/subscriptions/local/schedulers/emulator/taskhubs/ZeusOrchestrationHub/orchestrations",
    "DTS orchestrations");

Source reference:
src/Aspire.Hosting.Azure.Functions/DurableTask/DurableTaskResourceExtensions.cs, in the AddTaskHub OnResourceReady callback.

Dominant language
C#
Stars
6.3k
Forks
992
Avg merge
2d 16h
Merged PRs (30d)
176

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/aspire

All issues in microsoft/aspire

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.