You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: