You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We would like to see a callback function to check if a condition is true to f.ex. end a digest or wait step.
If leveraged, this could also lead to be used as schedules for checking workflows to be run. But this may be out of scope.
🎤 Why is this feature needed ?
This would enable followup emails or even responses to interaction more smoothly and would reduce the developers need to setup complex cronjobs for this.
Use-Cases I can think of:
Error was resolved
Errors & Warnings Workflow detected an error with a high priority, so it will skip the current digest and will populate all current digest events and the current event
Thanks for your reply f.ex. in discord => maybe such use-cases can get much more complex to be honest :)
✌️ How do you aim to achieve this?
condition check function => the function which will check if a condition was met
ttl or trigger event-selector => define how often this should be triggered
BackOff strategy => to reduce systemload after a while
🔄️ Additional Information
No response
👀 Have you spent some time to check if this feature request has been raised before?
🔖 Feature description
We would like to see a callback function to check if a condition is true to f.ex. end a digest or wait step.
If leveraged, this could also lead to be used as schedules for checking workflows to be run. But this may be out of scope.
🎤 Why is this feature needed ?
This would enable followup emails or even responses to interaction more smoothly and would reduce the developers need to setup complex cronjobs for this.
Use-Cases I can think of:
✌️ How do you aim to achieve this?
🔄️ Additional Information
No response
👀 Have you spent some time to check if this feature request has been raised before?
🏢 Have you read the Code of Conduct?
Are you willing to submit PR?
None
The text was updated successfully, but these errors were encountered: