Skip to content

Allow catch node on any task #1091

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.

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

Open
LeifLazar opened this issue Mar 24, 2025 · 4 comments
Open

Allow catch node on any task #1091

LeifLazar opened this issue Mar 24, 2025 · 4 comments
Labels
area: spec Changes in the Specification change: feature New feature or request. Impacts in a minor version change type: feature

Comments

@LeifLazar
Copy link

What would you like to be added?

Simplify error handling by allowing a catch node on any task.

Based on this discussion: #1085

Proposal(s):

No response

Alternative(s):

No response

Additional info:

No response

Community Notes

  • Please vote by adding a 👍 reaction to the feature to help us prioritize.
  • If you are interested to work on this feature, please leave a comment.
@ricardozanini ricardozanini added change: feature New feature or request. Impacts in a minor version change area: spec Changes in the Specification labels Mar 24, 2025
@ricardozanini
Copy link
Member

@LeifLazar, many thanks for opening this issue. Are you planning to work on this issue?

@LeifLazar
Copy link
Author

@LeifLazar, many thanks for opening this issue. Are you planning to work on this issue?

Yup, I'm on it right now. Having some trouble setting up Synapse for testing but I think I'll have it figured out.

@cdavernas
Copy link
Member

@LeifLazar Don't hesitate to reach out to me on Slack or LinkedIn if you need help with Synapse 😉

@LeifLazar
Copy link
Author

@cdavernas I dropped a message on Slack but in the meantime I managed to get Synapse up and running. It was not a simple task 😁. I created an issue on the Synapse repo with my findings. I can open a p.r. for those changes as well, once they're discussed.

I'll resume working on this in the next few days.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: spec Changes in the Specification change: feature New feature or request. Impacts in a minor version change type: feature
Projects
Status: Backlog
Development

No branches or pull requests

3 participants