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

Smart Timeouts #744

Open
jensg-st opened this issue Jan 19, 2023 · 0 comments
Open

Smart Timeouts #744

jensg-st opened this issue Jan 19, 2023 · 0 comments
Labels
improvement New feature or request

Comments

@jensg-st
Copy link
Member

Is your feature request related to a problem? Please describe.

At the moment the workflows, subflows, consumeEvent and action timeouts are independent from each other, e.g. if an action has a timeout set for 30 minutes it will be killed by the default workflow timeout of 15 minutes so the timeout for the workflow has to be changed manually. That gets worse if there are subflows involved and they are 2 levels down in the hierarchy. The manual configuration has to configured all the way up to the parent.

Describe the solution you'd like

There should be at least some smarts calculating the minimum timeout required to run the workflow. At least if they are set manually. If a consumeEvent or action has an explicit timeout set the workflow timeout should be that plus default 15 minutes if the workflow timeout is not set. This could still fail if there is a indirect subflow with longer timeouts but this calculation would be an improvement.

@jensg-st jensg-st added the improvement New feature or request label Jan 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
improvement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant