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
Support return commands from previous decision to save overhead of calling waitUntil #299
Comments
One idea is to let the state decision to call the next state ‘a waitUntil api in advance (it even has the input already). And then provide a flag in workflow state option to opt in this optimization. We may provide an IDE plugin to hint user to use this feature— based on the implementation of waitUntil |
WaitUntilEagerly , not persistence or communication. User code shouldn’t call external api |
The implementation will be similar to iwf/service/interpreter/workflowImpl.go Line 546 in 34052f7
|
A lot of the waitUntil api is quite simple —- just return a static command request. For those cases, it’s more efficient to return them from the previous state decision
The text was updated successfully, but these errors were encountered: