Skip to content

Conversation

spkane31
Copy link
Contributor

@spkane31 spkane31 commented Jul 30, 2025

What was changed

  • Added pause information display for pending activities in temporal workflow describe command. Shows Paused status, PauseTime, and PausedBy fields when activities are paused.
  • Add Workflow Pause information to temporal workflow describe

Why?

Users get visibility into whether activities are paused when troubleshooting workflow execution issues.

Checklist

  1. Closes #[issue-number]

  2. How was this tested:
    Run temporal workflow describe on workflows with paused activities to verify pause information displays correctly.

  3. Any docs updates needed?
    No documentation updates required - this is additional output in existing command.

Requires this server pr to be merged first

@spkane31 spkane31 requested a review from gow July 30, 2025 21:50
@spkane31 spkane31 requested review from bergundy and cretz August 12, 2025 22:59
@spkane31 spkane31 marked this pull request as ready for review August 12, 2025 23:00
@spkane31 spkane31 requested review from a team as code owners August 12, 2025 23:00
Copy link
Member

@cretz cretz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM pending discussions on the API itself (so can't mark approved yet)

}

if pauseInfo := resp.GetWorkflowPauseInfo(); pauseInfo != nil {
cctx.Printer.Println(color.MagentaString("Paused Activities: %v", len(pauseInfo.GetActivityPauseInfos())))
Copy link
Member

@cretz cretz Aug 13, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Mentioned in other context, but this isn't actually "paused activities" IMO, that is shown in "pending activities that are paused" above, this is "settings for future activity pausing".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants