-
Notifications
You must be signed in to change notification settings - Fork 16
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
Support for retries and timeout #130
Comments
Hello @Purushottamlpa, thank you for your interest in our work! If this is a bug report, please provide the minimum viable code and steps to reproduce your issue, otherwise we can not help you. |
👋 @Purushottamlpa, Thank you for submitting your issue. Currently is there no retry functionallity build into Semaphore. Flow retries could be implemented through middleware. Could you maybe elaborate a little bit on why you need this feature?
It is possible to set request duration timeouts inside the listeners. There is currently no possibility of defining a custom timeout for a specific flow. |
Thanks @jeroenrinzema. My query is within in a flow, if an HTTP call fails, is there any inbuilt support to put a delay in flow and retry failed service with configurable delay. |
Hi @Purushottamlpa, There is currently no built-in support for such use-case. It should be possible to implement this inside the node caller (https://github.com/jexia/semaphore/blob/master/pkg/flow/caller.go#L77-L90). An additional option has to be introduced inside the semaphore/pkg/providers/hcl/specs.go Lines 545 to 566 in eed88a8
|
Hi,
Is there support for retry and orchestrator side timeout option available in Semaphore?
The text was updated successfully, but these errors were encountered: