W Chan

If the action runner process dies unexpectedly while an action execution is still executing, the action execution will be stuck in a running state because the action runner process didn't...

For the orquesta workflow engine, rerunning/restarting WF from failed task is not supported yet. It is currently WIP and planned for a future release.

I think there are different things being communicated here. As I understand, 1) there is the case where the action runner dies while executing an action for a task and...

Currently, GC will `cancel` the workflow execution if it has been pass max idle time without any activity (i.e. active == task execution still executing). The current GC does not...

This is not currently prioritized for the next v3.2 release and we already started on v3.2. If this is something the community needs, st2 is open source and we welcome...

Currently, there is already a `notify` parameter that can be specified in st2 action execution to specify which task to notify on. An example is located at https://github.com/StackStorm/st2/blob/master/st2tests/st2tests/fixtures/packs/orquesta_tests/actions/notify.yaml. However, it...

@moejarv You can use this example at https://github.com/StackStorm/st2/blob/master/st2tests/st2tests/fixtures/packs/orquesta_tests/actions/notify.yaml to specify a simple notify for the list of tasks that you want to get notification on. As for the original request...

The following is an option that we have been talking about. ``` tasks: task1: ... next: - when: and: - when: do: task2 - when: and: - when: do: task3...

@dzimine @bigmstone Any feedback for us on the proposed design above?

@bigmstone I haven't forgotten your feedback above, i'm just not sure yet.