feat(cli): Add workflow refresh tasks command (#7657)

<!-- 1-2 line summary of WHAT changed technically:
- Always link the relevant projects GitHub issue, unless it is a minor
bugfix
- Good: "Modified FailoverDomain mapper to allow null ActiveClusterName
#320"
- Bad: "added nil check" -->
**What changed?**
This PR exposes the existing workflow API through a new CLI command
**workflow refresh-tasks**, enabling users without admin access to
refresh tasks for their workflows when tasks are lost or stuck.
Usage of the command: cadence --domain <domain> workflow refresh-tasks
-w <workflow_id> -r <run_id>

<!-- Your goal is to provide all the required context for a future
maintainer
to understand the reasons for making this change (see
https://cbea.ms/git-commit/#why-not-how).
How did this work previously (and what was wrong with it)? What has
changed, and why did you solve it
this way?
- Good: "Active-active domains have independent cluster attributes per
region. Previously,
modifying cluster attributes required spedifying the default
ActiveClusterName which
updates the global domain default. This prevents operators from updating
regional
configurations without affecting the primary cluster designation. This
change allows
  attribute updates to be independent of active cluster selection."
- Bad: "Improves domain handling" -->
**Why?**
Currently, refreshing workflow tasks is only available via cadence admin
workflow refresh, which requires admin-level permissions. However, the
equivalent RefreshWorkflowTasks API already exists on the workflow
frontend service with write-level permissions, so adding this workflow
refresh CLI command to allow non-admin users to refresh workflow tasks.

<!-- Include specific test commands and setup. Please include the exact
commands such that
another maintainer or contributor can reproduce the test steps taken. 
- e.g Unit test commands with exact invocation
`go test -v ./common/types/mapper/proto -run TestFailoverDomainRequest`
- For integration tests include setup steps and test commands
Example: "Started local server with `./cadence start`, then ran `make
test_e2e`"
- For local simulation testing include setup steps for the server and
how you ran the tests
- Good: Full commands that reviewers can copy-paste to verify
- Bad: "Tested locally" or "Added tests" -->
**How did you test it?**
- Unit tests: go test -run Test_RefreshWorkflowTasks ./tools/cli/...
- Manual test by building the CLI locally and running `cadence workflow
refresh-tasks`

<!-- If there are risks that the release engineer should know about
document them here.
For example:
- Has an API/IDL been modified? Is it backwards/forwards compatible? If
not, what are the repecussions?
- Has a schema change been introduced? Is it possible to roll back?
- Has a feature flag been re-used for a new purpose? 
- Is there a potential performance concern? Is the change modifying core
task processing logic?
- If truly N/A, you can mark it as such -->
**Potential risks**
Low risk as it is adding a new CLI command.

<!-- If this PR completes a user facing feature or changes functionality
add release notes here.
Your release notes should allow a user and the release engineer to
understand the changes with little context.
Always ensure that the description contains a link to the relevant
GitHub issue. -->
**Release notes**
CLI: Added cadence workflow refresh command to refresh workflow tasks
without requiring admin permissions. This command uses the workflow API
with write-level authorization, making it accessible to domain owners
and users with write access. Previously, refreshing workflow tasks was
only available via the admin CLI.

<!-- Consider whether this change requires documentation updates in the
Cadence-Docs repo
- If yes: mention what needs updating (or link to docs PR in
cadence-docs repo)
- If in doubt, add a note about potential doc needs
- Only mark N/A if you're certain no docs are affected -->
**Documentation Changes**
Command: cadence workflow refresh-tasks
Refreshes workflow tasks to resume progress. This is useful when
workflow tasks are lost or stuck due to transient failures.
Usage:
cadence --domain <domain> workflow refresh-tasks -w <workflow_id> -r
<run_id>

---

## Reviewer Validation

**PR Description Quality** (check these before reviewing code):

- [ ] **"What changed"** provides a clear 1-2 line summary
  - [ ] Project Issue is linked
- [ ] **"Why"** explains the full motivation with sufficient context
- [ ] **Testing is documented:**
- [ ] Unit test commands are included (with exact `go test` invocation)
- [ ] Integration test setup/commands included (if integration tests
were run)
  - [ ] Canary testing details included (if canary was mentioned)
- [ ] **Potential risks** section is thoughtfully filled out (or
legitimately N/A)
- [ ] **Release notes** included if this completes a user-facing feature
- [ ] **Documentation** needs are addressed (or noted if uncertain)

---------

Signed-off-by: Gaziza Yestemirova <gaziza@uber.com>

Author: gazi-yestemirova

tools/cli/workflow.go

@@ -45,6 +45,13 @@ func newWorkflowCommands() []*cli.Command {
 			Flags:   flagsForExecution,
 			Action:  DiagnoseWorkflow,
 		},
+		{
+			Name:    "refresh-tasks",
+			Aliases: []string{"rt"},
+			Usage:   "refreshes all the workflow tasks to resume progress",
+			Flags:   flagsForExecution,
+			Action:  RefreshWorkflowTasks,
+		},
 		{
 			Name:        "activity",
 			Aliases:     []string{"act"},

tools/cli/workflow_commands.go

@@ -134,6 +134,43 @@ func DiagnoseWorkflow(c *cli.Context) error {
 	return nil
 }
 
+// RefreshWorkflowTasks refreshes all the tasks of a workflow
+func RefreshWorkflowTasks(c *cli.Context) error {
+	wfClient, err := getWorkflowClient(c)
+	if err != nil {
+		return err
+	}
+
+	domain, err := getRequiredOption(c, FlagDomain)
+	if err != nil {
+		return commoncli.Problem("Required flag not found: ", err)
+	}
+	wid, err := getRequiredOption(c, FlagWorkflowID)
+	if err != nil {
+		return commoncli.Problem("Required flag not found: ", err)
+	}
+	rid := c.String(FlagRunID)
+
+	ctx, cancel, err := newContext(c)
+	if err != nil {
+		return commoncli.Problem("Error creating context: ", err)
+	}
+	defer cancel()
+
+	err = wfClient.RefreshWorkflowTasks(ctx, &types.RefreshWorkflowTasksRequest{
+		Domain: domain,
+		Execution: &types.WorkflowExecution{
+			WorkflowID: wid,
+			RunID:      rid,
+		},
+	})
+	if err != nil {
+		return commoncli.Problem("Refresh workflow tasks failed.", err)
+	}
+	fmt.Println("Refresh workflow tasks succeeded.")
+	return nil
+}
+
 // ShowHistory shows the history of given workflow execution based on workflowID and runID.
 func ShowHistory(c *cli.Context) error {
 	wid, err := getRequiredOption(c, FlagWorkflowID)

tools/cli/workflow_commands_test.go

@@ -2579,6 +2579,79 @@ func Test_DescribeWorkflow_Errors(t *testing.T) {
 	assert.ErrorContains(t, err, fmt.Sprintf("%s is required", FlagWorkflowID))
 }
 
+func Test_RefreshWorkflowTasks(t *testing.T) {
+	tests := []struct {
+		name        string
+		setupMock   func(*frontend.MockClient)
+		args        []clitest.CliArgument
+		errContains string
+	}{
+		{
+			name:        "missing domain",
+			setupMock:   func(_ *frontend.MockClient) {},
+			args:        []clitest.CliArgument{},
+			errContains: "Required flag not found",
+		},
+		{
+			name:      "missing workflowID",
+			setupMock: func(_ *frontend.MockClient) {},
+			args: []clitest.CliArgument{
+				clitest.StringArgument(FlagDomain, "test-domain"),
+			},
+			errContains: "Required flag not found",
+		},
+		{
+			name: "success",
+			setupMock: func(client *frontend.MockClient) {
+				client.EXPECT().RefreshWorkflowTasks(gomock.Any(), &types.RefreshWorkflowTasksRequest{
+					Domain: "test-domain",
+					Execution: &types.WorkflowExecution{
+						WorkflowID: "test-workflow-id",
+						RunID:      "test-run-id",
+					},
+				}).Return(nil)
+			},
+			args: []clitest.CliArgument{
+				clitest.StringArgument(FlagDomain, "test-domain"),
+				clitest.StringArgument(FlagWorkflowID, "test-workflow-id"),
+				clitest.StringArgument(FlagRunID, "test-run-id"),
+			},
+			errContains: "",
+		},
+		{
+			name: "api error",
+			setupMock: func(client *frontend.MockClient) {
+				client.EXPECT().RefreshWorkflowTasks(gomock.Any(), gomock.Any()).
+					Return(errors.New("api error"))
+			},
+			args: []clitest.CliArgument{
+				clitest.StringArgument(FlagDomain, "test-domain"),
+				clitest.StringArgument(FlagWorkflowID, "test-workflow-id"),
+				clitest.StringArgument(FlagRunID, "test-run-id"),
+			},
+			errContains: "Refresh workflow tasks failed",
+		},
+	}
+
+	for _, tt := range tests {
+		t.Run(tt.name, func(t *testing.T) {
+			mockCtrl := gomock.NewController(t)
+			serverFrontendClient := frontend.NewMockClient(mockCtrl)
+			app := NewCliApp(&clientFactoryMock{
+				serverFrontendClient: serverFrontendClient,
+			})
+			tt.setupMock(serverFrontendClient)
+			ctx := clitest.NewCLIContext(t, app, tt.args...)
+			err := RefreshWorkflowTasks(ctx)
+			if tt.errContains == "" {
+				assert.NoError(t, err)
+			} else {
+				assert.ErrorContains(t, err, tt.errContains)
+			}
+		})
+	}
+}
+
 func Test_ObserveHistory_MissingFlags(t *testing.T) {
 	app := NewCliApp(&clientFactoryMock{})
 	set := flag.NewFlagSet("test", 0)