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.

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

Introduce failure handling and retry mechanisms for a step in defined workflow #75

Open
priyaaank opened this issue Nov 2, 2020 · 0 comments
Labels
enhancement New feature or request
Projects

Comments

@priyaaank
Copy link
Member

Introduce workflow primitives
Introduce workflow primitives like failure handling and retry mechanism

  • Failure handling
  • Retry

Consider existing process modeling steps by various workflow management tools
We need to be able to define a sub-workflow for failure handling. In addition to that, we should be able to specify how to retry should be done. The retry can be immediate, with delay or with an exponential backoff in the initial implementation. In addition to that failure, the workflow should be able to raise an event. The key distinction between an event and a step is that event does not wait for a response coming back from an event. Although event failure should be cared about and be handled as well. If the event trigger fails, an error should be captured in the service request output.

Describe alternatives you've considered
None.

Additional context
We assume that events can be asynchronous or synchronous and can be thrown using any of the support communication protocols.

@priyaaank priyaaank added the enhancement New feature or request label Nov 2, 2020
@priyaaank priyaaank added this to To do in clamp via automation Nov 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
clamp
  
To do
Development

No branches or pull requests

1 participant