Skip to content

docs: add error handling concepts#4605

Merged
lennessyy merged 14 commits into
mainfrom
error-handling-concepts
Jun 12, 2026
Merged

docs: add error handling concepts#4605
lennessyy merged 14 commits into
mainfrom
error-handling-concepts

Conversation

@lennessyy

@lennessyy lennessyy commented May 21, 2026

Copy link
Copy Markdown
Contributor

What does this PR do?

  • Ports some error handling corse content over to docs

Notes to reviewers

┆Attachments: EDU-6408 docs: add error handling concepts

@vercel

vercel Bot commented May 21, 2026

Copy link
Copy Markdown

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

Project Deployment Actions Updated (UTC)
temporal-documentation Ready Ready Preview, Comment Jun 12, 2026 12:27am

Request Review

@github-actions

github-actions Bot commented May 21, 2026

Copy link
Copy Markdown
Contributor

…on-failures

- Add PHP to SDK base class list and add "for example" qualifier
- Convert Task vs Execution failures section to comparison table
- Remove detecting-application-failures.mdx (content superseded by
  failures-and-error-handling landing page)
- Rename sidebar labels to "Detecting Activity failures" and
  "Detecting Workflow failures"
- Add redirect from old page to new landing page
- Update encyclopedia index link
@lennessyy lennessyy marked this pull request as ready for review June 9, 2026 00:16
@lennessyy lennessyy requested a review from a team as a code owner June 9, 2026 00:16
- Define Temporal failures as SDK error types that surface to application
  code, distinct from platform failures
- Clarify that platform failures never produce Temporal failure objects
- Scope the failure types table explicitly as Temporal failure types
@vercel

vercel Bot commented Jun 10, 2026

Copy link
Copy Markdown

Deployment failed with the following error:

The `vercel.json` schema validation failed with the following message: `redirects[0]` should NOT have additional property `permenant`

Learn More: https://vercel.com/docs/concepts/projects/project-configuration

- Rename error-handling-strategy to error-handling
- Add cross-links to Retry Policy, Application Failure, detecting
  failures, idempotency, and use cases pages
- Trim Saga section to brief description with link out
- Update all references in sidebar and encyclopedia pages
Do not wrap Application Failures in generic language errors (such as `Error` in TypeScript, `Exception` in Python, or `fmt.Errorf` in Go), as this causes the SDK to treat the error as a new, retryable failure.
:::

This behavior is consistent across all SDKs (Go, Java, TypeScript, Python, and .NET).

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

missing Ruby and Rust

### Workflow Execution failures

An Activity failure does not directly cause a Workflow Execution failure.
If an Activity fails and the error is not handled in the Workflow code (or is intentionally re-raised), the Workflow Execution fails.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

is not handled in the Workflow code

Not sure if it's just me, but this seems a little vague. Maybe it'd be more clear to also state "not handling" means letting the activity error propagate out of the WF function?

@lennessyy lennessyy enabled auto-merge (squash) June 12, 2026 00:26
@lennessyy lennessyy disabled auto-merge June 12, 2026 00:26
@lennessyy lennessyy merged commit b4ac037 into main Jun 12, 2026
12 checks passed
@lennessyy lennessyy deleted the error-handling-concepts branch June 12, 2026 00:28
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.

3 participants