st2 Orquesta sub-workflow always get stuck

One of orquesta sub-workflow alaways get stuck after scheduled.

Version is v3.4.1 running on RHEL 7

In the chart, orqusta sub-flow is scheduled at 03:35:12UTC with running status, but the first action running at 03:43:12UTC, there are more than 8 minutes pending here. Seems there is no other oquesta flows like this on my st2 , only this one has such issue.

I checked st2scheduler.log, st2actionrunner.log and st2workflowengine.log, there is no excetion and error during this subflow execution.

Do you have any suggestion how to identify problem? and what need I pay more attention when developing orquesta workflow?

Thanks!

May 31 '21 06:05 hgjsj

I think "slow" is a better word to describe this. The word "stuck" would seem to indicate that the sub-workflow never gets executed, which isn't the case based on your screenshot.

There are some performance improvements that have been added since ST2 v3.4.1, and version 3.5.0 should be out in a few weeks. You can either try an unstable build (built nightly), or a build from unstable-staging (built on every merge to master), or you can wait to see if version 3.5.0 improves this for you.

Jun 14 '21 17:06 blag

Thnaks for your reply. This issue temp fixed after splite this oquesta flow to two, the waiting time decrease to a minute. Probably old flow has too much “when” statements and each branch published many variables, this made engine crazy. Looking forward to addressing performance in new version.

Jun 15 '21 02:06 hgjsj

Thanks for contributing to this issue. As it has been 90 days since the last activity, we are automatically marking is as stale. If this issue is not relevant or applicable anymore (problem has been fixed in a new version or similar), please close the issue or let us know so we can close it. On the contrary, if the issue is still relevant, there is nothing you need to do, but if you have any additional details or context which would help us when working on this issue, please include it as a comment to this issue.

Apr 16 '22 05:04 stale[bot]

st2 3.5.0, on Python 3.6.8 I have the same problem

Jan 13 '23 10:01 BearGuardian

@hgjsj and @syz951127 Seems the issue is same as the one fixed as part of change https://github.com/StackStorm/orquesta/pull/239, which is part of st2 3.6.0, Can you try with 3.6.0

Apr 01 '23 15:04 yogeshgoyal26

@yogeshgoyal26 Already upgraded to v3.8.0. Performance has bigger improvement than 3.4.1, thank you.

Apr 03 '23 02:04 hgjsj