Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
fjtirado opened this issue Feb 22, 2024 · 2 comments
Assignees

Comments

@fjtirado
Copy link
Collaborator

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
Copy link
Member

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

@fjtirado
Copy link
Collaborator Author

It is addressed by #770

@github-project-automation github-project-automation bot moved this from Backlog to Done in Progress Tracker Mar 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

No branches or pull requests

2 participants