Skip to content

Support for sub-orchestration tags when a retry policy is specified #559

Closed
#603
Closed
Support for sub-orchestration tags when a retry policy is specified#559
#603
Labels
P2

Description

@sophiatev
sophiatev
opened on Dec 12, 2025

Currently there is no support for adding both a retry policy and tags when creating a suborchestration. This is due to the fact that no such overload exists in the DT.Core methods. This would first need to be addressed in that repo before a fix can be added here.

Activity

  1. sophiatev
    added
    P2
    on Dec 12, 2025

  2. YunchuWang commented on Dec 16, 2025

    @YunchuWang
    wangbill (YunchuWang)
    on Dec 16, 2025
    Member

    #558

  3. wangbill (YunchuWang)
    added
    pending release
    on Dec 16, 2025
  4. sophiatev
    removed
    pending release
    on Dec 29, 2025
  5. sophiatev
    closed this as completedin #603on Jan 6, 2026

  6. github-actions commented on Mar 13, 2026

    @github-actions
    github-actionsBot
    on Mar 13, 2026 – with GitHub Actions
    Contributor

    Issue Triage

    Classification: triage/already-fixed

    Reasoning:
    Closed. Sub-orchestration tags with retry policy support has been addressed.

    Automated fix candidate: No

    • Issue is already closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions