temporalio / temporalio/temporal

Unpaused schedules should not be immediately deleted

Open
#9,752 3 comments 0 reactions 1 assignee View on GitHub

@chaptersix is already working on this.

Since Apr 16, 2026.

bug schedules
Dominant language
Go
Stars
23.2k
Forks
1.9k
Avg merge
2d 8h
Merged PRs (30d)
228

Description

Expected Behavior

  • Retention period does not apply to a paused schedule
  • Unpausing a schedule should reset the retention timer

Actual Behavior

  • If a schedule is paused for longer than the retention period with no actions fired or updates made, unpausing it causes the backing workflow to close.

Steps to Reproduce

  1. Create a schedule
  2. Pause the schedule
  3. Wait longer than the retention period
  4. Unpause the schedule

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.