Skip to content

(status: incorporating feedback) Endpoints update + Namespace best practices consolidation + Clarify that HA replica pricing only begins when the replica is "active"#4197

Open
lukeknep wants to merge 4 commits intomainfrom
clarify-ha-pricing
Open

(status: incorporating feedback) Endpoints update + Namespace best practices consolidation + Clarify that HA replica pricing only begins when the replica is "active"#4197
lukeknep wants to merge 4 commits intomainfrom
clarify-ha-pricing

Conversation

@lukeknep
Copy link
Contributor

@lukeknep lukeknep commented Feb 6, 2026

What does this PR do?

Clarifies that the 2x multiplier only happens once the replica is "active," not while it is being created (and not to anything that completed before it was created).

Slack: https://temporaltechnologies.slack.com/archives/C09J34DBURK/p1767723787421509

┆Attachments: EDU-5893 Clarify that HA replica pricing only begins when the replica is "active"

@lukeknep lukeknep requested review from a team and tlotemporal as code owners February 6, 2026 22:37
@vercel
Copy link

vercel bot commented Feb 6, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
temporal-documentation Error Error Feb 9, 2026 2:29pm

Request Review

@github-actions
Copy link
Contributor

github-actions bot commented Feb 6, 2026

📖 Docs PR preview links

Copy link

@tlotemporal tlotemporal left a comment

Choose a reason for hiding this comment

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

Pricing page udpate LGTM

permitted at the Namespace level. Isolating applications or environments (development, test, staging, production)
should take this into consideration.
- A Namespace is provisioned with an endpoint for executing your Workflows. Accessing a Namespace from a Temporal Client
- A Namespace is provisioned with [endpoints](constraints-and-limitations) for executing your Workflows. Accessing a Namespace from a Worker or Temporal Client
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
- A Namespace is provisioned with [endpoints](constraints-and-limitations) for executing your Workflows. Accessing a Namespace from a Worker or Temporal Client
- A Namespace is provisioned with endpoints for executing your Workflows. Accessing a Namespace from a Worker or Temporal Client

Copy link
Contributor

@flippedcoder flippedcoder Feb 9, 2026

Choose a reason for hiding this comment

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

Was that the link you meant to put for endpoints? It links to the top of the section.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Oops, good catch. Will change to the correct one (#access-namespaces)

@flippedcoder flippedcoder self-assigned this Feb 9, 2026
@lukeknep lukeknep changed the title Clarify that HA replica pricing only begins when the replica is "active" (edit: merging with another PR) Endpoints update + Namespace best practices consolidation + Clarify that HA replica pricing only begins when the replica is "active" Feb 9, 2026
@lukeknep lukeknep changed the title (edit: merging with another PR) Endpoints update + Namespace best practices consolidation + Clarify that HA replica pricing only begins when the replica is "active" (status: incorporating feedback) Endpoints update + Namespace best practices consolidation + Clarify that HA replica pricing only begins when the replica is "active" Feb 9, 2026
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.

4 participants