Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Decide/apply/clarify ambiguous failure behavior in signals and workflows #482

Open
3 of 8 tasks
cretz opened this issue May 17, 2024 · 0 comments
Open
3 of 8 tasks

Decide/apply/clarify ambiguous failure behavior in signals and workflows #482

cretz opened this issue May 17, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@cretz
Copy link
Member

cretz commented May 17, 2024

Describe the solution you'd like

Related to #481. Currently exceptions in signal handlers are treated as if they were thrown in the main workflow function. But what happens when workflow function and signal handler both throw an exception in the same task? Which takes precedence?

The task is to confirm how each SDK does it today, if it will change with #481, and what if anything we want to do about it.

Per-SDK Tickets

TODO - pending outcome

  • Go -
  • Java -
  • Core - N/A
  • TypeScript -
  • Python -
  • .NET -
  • PHP -
  • Temporal CLI - N/A
@cretz cretz added the enhancement New feature or request label May 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@cretz