This site is in read only mode. Please continue to browse, but replying, likes, and other actions are disabled for now.

⚠️ We've moved!

Hi there!

To reduce project dependency on 3rd party paid services the StackStorm TSC has decided to move the Q/A from this forum to Github Discussions. This will make user experience better integrated with the native Github flow, as well as the questions closer to the community where they can provide answers.

Use 🔗 Github Discussions to ask your questions.

Orquesta workflow stuck in running state

We have been seeing few random instances where workflow execution went back to running state after it had completed and is stuck in running state after that.

Action execution log field:
[ { “timestamp” : ISODate(“2021-03-27T13:24:52.932Z”), “status” : “requested” }, { “timestamp” : ISODate(“2021-03-27T13:24:54.938Z”), “status” : “scheduled” }, { “timestamp” : ISODate(“2021-03-27T13:25:00.200Z”), “status” : “running” }, { “timestamp” : ISODate(“2021-03-27T13:25:40.857Z”), “status” : “succeeded” }, { “timestamp” : ISODate(“2021-03-27T13:25:43.470Z”), “status” : “running” } ]

Liveaction and workflow execution object are in succeeded state. The workflow calls an action which had completed at end_timestamp: Sat, 27 Mar 2021 13:25:41 UTC which is after the workflow had succeeded.

st2 3.2.0, on Python 3.6.9