Add long_idle_workflow scenario#367
Open
lilydoar wants to merge 1 commit into
Open
Conversation
Exercises long-lived, mostly idle workflows with optional periodic activity bursts and continue-as-new chains. Stresses history retention, idle timer scheduling, and steady-state fleet cost. stack-info: PR: #367, branch: lilydoar/stack/1
lilydoar
force-pushed
the
lilydoar/stack/1
branch
from
43cd69e to
8cc1b2f
Compare
This was referenced May 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Stacked PRs:
Add long_idle_workflow scenario
Exercises long-lived, mostly idle workflows with optional periodic activity
bursts and continue-as-new chains. Stresses history retention, idle timer
scheduling, and steady-state fleet cost.