Skip to content

Add WorkflowUpdateResultException#526

Closed
roxblnfk wants to merge 1 commit into
masterfrom
update-result-exception
Closed

Add WorkflowUpdateResultException#526
roxblnfk wants to merge 1 commit into
masterfrom
update-result-exception

Conversation

@roxblnfk

@roxblnfk roxblnfk commented Nov 13, 2024

Copy link
Copy Markdown
Collaborator

What was changed

Added the WorkflowUpdateResultException, which is thrown by UpdateHandle->getResult() when a Workflow Update Request is stuck in the ADMITTED status. This situation can occur when the Workflow neither accepts nor rejects the Update due to:

  • No available workers
  • Workflow Task fails in the same tick

Why?

Developers need to distinguish between null as an actual result of a Workflow Update action and "no result."
Prior to this patch, the code used assert($result === null), which did not align with reality. Additionally, assertions are typically disabled in production environments.

Checklist

  1. Closes

  2. How was this tested:

  1. Any docs updates needed?

@vercel

vercel Bot commented Nov 13, 2024

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
php ✅ Ready (Inspect) Visit Preview 💬 Add feedback Nov 13, 2024 0:27am

@Sushisource

Copy link
Copy Markdown
Member

@roxblnfk So I think we don't need to do this at all - in the other SDKs we just keep trying until we hit the timeout or are cancelled and we should mirror that behavior here.

@roxblnfk

roxblnfk commented Apr 8, 2025

Copy link
Copy Markdown
Collaborator Author

Replaced with #591

@roxblnfk roxblnfk closed this Apr 8, 2025
@roxblnfk
roxblnfk deleted the update-result-exception branch April 9, 2025 09:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants