Skip to content

Clarify instance reuse behavior after session ends#524

Merged
markbackman merged 1 commit intomainfrom
clarify-instance-reuse-after-deployment
Feb 5, 2026
Merged

Clarify instance reuse behavior after session ends#524
markbackman merged 1 commit intomainfrom
clarify-instance-reuse-after-deployment

Conversation

@jamsea
Copy link
Contributor

@jamsea jamsea commented Feb 5, 2026

Summary

  • Clarifies in the deploy and scaling docs that when a new deployment is pushed, instances running the prior image are discarded once their sessions end (not returned to the pool)
  • Clarifies that when there is no new deployment, instances are returned to the pool and remain available to serve new sessions during a cooldown period
  • Updates the agent lifecycle section in the scaling docs to explicitly describe both behaviors

Test plan

  • Verify deploy.mdx renders correctly with the new <Note> block
  • Verify scaling.mdx agent lifecycle step reads clearly

🤖 Generated with Claude Code

Make it explicit that instances are only returned to the pool when there
is no new deployment. When a new deployment has been pushed, instances
running the prior image are discarded once their sessions conclude.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

This PR clarifies the instance lifecycle behavior in Pipecat Cloud documentation, specifically addressing how instances are handled after sessions end in two different scenarios: normal operation vs. when a new deployment is pushed.

Changes:

  • Updated scaling.mdx to explicitly describe that instances are returned to the pool normally, but discarded when a new deployment exists
  • Updated deploy.mdx to clarify that old image instances are discarded (not recycled) after a new deployment
  • Added a Note block in deploy.mdx explaining the contrast between the two behaviors and mentioning the cooldown period

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File Description
deployment/pipecat-cloud/fundamentals/scaling.mdx Updated agent lifecycle auto-scaling step to clarify instance reuse vs. discard behavior based on deployment status
deployment/pipecat-cloud/fundamentals/deploy.mdx Added clarification that old instances are discarded after new deployment, plus Note block explaining both behavioral scenarios

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@jamsea jamsea self-assigned this Feb 5, 2026
@jamsea jamsea requested a review from markbackman February 5, 2026 03:23
Copy link
Contributor

@markbackman markbackman left a comment

Choose a reason for hiding this comment

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

Nice updates. Thanks!

@markbackman markbackman merged commit 685855c into main Feb 5, 2026
8 checks passed
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