search

serverlessworkflow / specification

Contains the official specification for the Serverless Workflow Domain Specific Language. It provides detailed guidelines and standards for defining, executing, and managing workflows in serverless environments, ensuring consistency and interoperability across implementations.
http://serverlessworkflow.io
Apache License 2.0
742 stars 147 forks source link

Timeout expiration behaviour, transition to an specific state, not the regular one #825

Closed fjtirado closed 7 months ago

fjtirado commented 8 months ago

What would you like to be added:

All the event timeouts configured for callback, event and switch states, should allow the definition of a timeout that, instead of moving to the next state defined in the transition property (or the equivalent property, depending on the state), can transition to a configurable state and then return the execution to the original state.

The reason for this change request is to allow executing validation tasks while another task is in pending state.

Additionally, these trigger-based states can be executed more than once, until a configured limit is reached (maybe similar to the retry definition, but not evaluated after failures of services)

Why is this needed:

cdavernas commented 7 months ago

@fjtirado this is addressed by the error refactor PR. Timeout should produce an error, which can they be handled as you see fit.

fjtirado commented 7 months ago

It is addressed by https://github.com/serverlessworkflow/specification/issues/770