W Chan

Also, as an alternative, user can also do the following right now where task1 publish and transition on succeeded to an empty task2. Task2 (no action defined) branches out with...

@emptywee The issue here is that result of action execution can be different for success and failure. What if I want to publish x on success (only in the result...

@emptywee You are not doing this doesn't mean it is not done by other users though. Among other use cases, it's common to publish certain variables on success but then...

This type of design discussion is needed to understand requirements and evaluate solution proposals. The person who is going to implement this feature will be able to look at the...

I don't have an opinion on your proposed solution atm. There is a workaround for the problem you stated. I am in no rush to make a decision on this...

I think there are two separate problems communicated here. 1. Current task transition with next/when/publish/do is very repetitive if there are more than one task transition. 2. There is a...

This issue has been brought up again in the community Slack channel. Please note that there is a workaround at https://github.com/StackStorm/orquesta/issues/116#issuecomment-478713066 which uses intermediate tasks. So far, the Orquesta workflow...

In current implementation, the retry is scoped to the task so it retry the task and not the items in the case of with items. We can add an option...

The following is one possible solution for the retry spec to support per-item retry. ``` retry: items: when: count: 3 delay: 1 ```

@kyildiz It was a proposal and not supported yet.