serverlessworkflow
Allow catch node on any task
What would you like to be added?
Simplify error handling by allowing a catch node on any task.
Based on this discussion: https://github.com/serverlessworkflow/specification/discussions/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.
@LeifLazar, many thanks for opening this issue. Are you planning to work on this issue?
@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.
@LeifLazar Don't hesitate to reach out to me on Slack or LinkedIn if you need help with Synapse 😉
@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.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.