Clarification on supporting multiple actions and actionMode in Operation State about wg-serverless HOT 3 CLOSED

@yzhao244
this is indeed a workflow definition design choice based on your requirements (whether to have a single function invocation in your actions or multiple).

A State (or Task in ASL as you mentioned) for us represents a unit of work.
An action definition can be part of this unit of work, but in some cases you can have multiple actions represent a single one.
Error handling in SW currently is based again, on errors raised during unit of work / state execution, and so are retry definitions.
So yes, the way of defining a retry definition for a single action (function invocation) is to have a single action associated with your action definition.

Do you have some use cases where you think this is better handled in a different way(s)?

from wg-serverless.

@yzhao244

One more thing - the project github repo is here: https://github.com/serverlessworkflow/specification
If you don't mind lets more our conversations there so community can see it better. Ty

from wg-serverless.

@tsurdilo I am very sorry that I opened issue here. I will create a new one there and close this one

from wg-serverless.