Unpaused schedules should not be immediately deleted

[chaptersix]

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

[gurudatta-patil]

Hi @chaptersix , I've submitted PR #9862 to address this. It ensures that the retention timer is reset when a schedule is unpaused, preventing the backing workflow from closing prematurely if the pause duration exceeded the retention period.

This is my first contribution to the project, so please let me know if there are any specific testing requirements or style adjustments needed!

[julianbradford19-png]

Thank you for submitting PR #9862 to address the retention timer issue for unpaused schedules.

…

On Wed, Apr 8, 2026, 11:01 AM Gurudatta Patil ***@***.***> wrote: *gurudatta-patil* left a comment (temporalio/temporal#9752) <#9752 (comment)> Hi @chaptersix <https://github.com/chaptersix> , I've submitted PR #9862 <#9862> to address this. It ensures that the retention timer is reset when a schedule is unpaused, preventing the backing workflow from closing prematurely if the pause duration exceeded the retention period. This is my first contribution to the project, so please let me know if there are any specific testing requirements or style adjustments needed! — Reply to this email directly, view it on GitHub <#9752 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/B74KUGZKNSVHGSDFPDJAEKD4UZZWVAVCNFSM6AAAAACXHX7RJSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DEMBXGY2TAMRXGU> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[chaptersix]

This bug only exists in the workflow backed scheduler and would require a workflow version change. Version changes usually require the multiple minor release to introduce due to our rollback safety requirement.
Given we plan to rollout the CHASM backed scheduler over the next few releases, it's not worth introducing a fix for this bugs.

We'll leave this issue open until the CHASM scheduler becomes the default backend.