Preserve activity tags across retry attempts

[Tsuyoshi Ushio (TsuyoshiUshio)]

Summary

Activity tags are currently dropped when an activity is retried. This causes retry attempts to lose metadata such as durabletask.displayName, so dashboards fall back to the registered function name even though the initial attempt used the caller-provided display name.

Raw orchestration history demonstrates the symptom: the initial taskScheduled event contains durabletask.displayName, while retry-generated taskScheduled events contain an empty tags map.

Root cause

When a retry timer fires, the worker reconstructs the activity schedule action from the saved original action but forwards only its name and input. The saved tags are not passed to the reconstructed action.

Fix

Copy the saved Activity tag map into each reconstructed schedule action. This preserves durabletask.displayName and all other caller-provided Activity tags without changing sub-orchestration retry behavior.

Regression coverage

Added an orchestration executor test that schedules a tagged Activity with a retry policy, fails two attempts, fires both retry timers, and verifies every retry-generated ScheduleTaskAction retains the original tags.

[Copilot]

🟢 Approval recommended

The change is narrowly scoped, includes a targeted regression test, and updates the changelog to reflect the user-visible behavior fix.

Pull request overview

This PR fixes a Durable Task Python SDK bug where ScheduleTaskAction tags (e.g., durabletask.displayName) were lost when an activity was rescheduled due to retries, causing retry attempts to drop caller-provided metadata.

Changes:

• Preserve activity ScheduleTaskAction.tags when reconstructing activity schedule actions after a retry timer fires.
• Add a regression test ensuring tags are retained for each retry-generated activity schedule action.
• Document the user-visible bug fix in the root changelog under Unreleased.

File summaries

File	Description
tests/durabletask/test_orchestration_executor.py	Adds a regression test validating that activity tags persist across retry attempts.
durabletask/worker.py	Copies tags from the saved original activity schedule action into the reconstructed retry schedule action.
CHANGELOG.md	Records the fix under ## Unreleased as a user-visible behavior correction.

Review details

• Files reviewed: 3/3 changed files
• Comments generated: 0
• Review effort level: Lite

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.