close
Skip to content

Update docs to refine explanations for non-determinism#4448

Draft
flippedcoder wants to merge 4 commits intomainfrom
mm/nondeterminism-clean-up
Draft

Update docs to refine explanations for non-determinism#4448
flippedcoder wants to merge 4 commits intomainfrom
mm/nondeterminism-clean-up

Conversation

@flippedcoder
Copy link
Copy Markdown
Contributor

@flippedcoder flippedcoder commented Apr 17, 2026

What does this PR do?

Some pages in the docs need to be updated so that determinism is better understood. Right now we say that Temporal is deterministic when really only Workflows are deterministic and Activities handle non-determinism operations.

Notes to reviewers

┆Attachments: EDU-6219 Update docs to refine explanations for non-determinism

@flippedcoder flippedcoder requested a review from a team as a code owner April 17, 2026 19:08
@vercel
Copy link
Copy Markdown

vercel Bot commented Apr 17, 2026

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

Project Deployment Actions Updated (UTC)
temporal-documentation Ready Ready Preview, Comment Apr 24, 2026 6:18pm

Request Review

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Apr 17, 2026

📖 Docs PR preview links

@cdavisafc
Copy link
Copy Markdown

Hi @flippedcoder - thanks so much for getting this ball rolling.

I'd like to draw your attention to a few comments in this doc - in particular, the ones around how LLMs pattern match rather than understand. I don't think it is enough to say "workflows are deterministic. activities are not"

I know that makes the task tricker - which is what I was poking at a bit with my suggestion that perhaps we take a crack at explaining replay without that word.

@flippedcoder
Copy link
Copy Markdown
Contributor Author

flippedcoder commented Apr 24, 2026

Hi @flippedcoder - thanks so much for getting this ball rolling.

I'd like to draw your attention to a few comments in this doc - in particular, the ones around how LLMs pattern match rather than understand. I don't think it is enough to say "workflows are deterministic. activities are not"

I know that makes the task tricker - which is what I was poking at a bit with my suggestion that perhaps we take a crack at explaining replay without that word.

@cdavisafc Thanks for sharing this! I see what you mean about that little nuance. So I went ahead and took a stab at explaining replay here.

It gave me an idea of a direction to go in. Maybe instead of just saying "workflows are deterministic. activities are not", what if we said something like "Workflows are deterministic, but the Activities they execute don't need to be"?

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