Is your feature request related to a problem? Please describe.
When executing many local activities in a row or parallel within a workflow task, (or a local activity is retrying), the workflow task is waiting until passed 80% of the workflow task timeout(10s). This could cause a big delay of query processing, or signal processing.
In certain scenarios, it's more flexible to let user workflow to decide when they can report the workflow task completed and then get(lease) a new workflow task to execute the next activities. This will then make it possible to process query task, or new signals.
Describe the solution you'd like
- LocalActivityOptions provides a flag to allow user to force complete current workflow task when it's completed and/or failed.
- alternatively, have an API like activity.forceCompleteWorkflowTask() to be invoked by user code
- It should be only a SDK feature, likely server doesn't need to do anything.
Additional context
Acknowledged by Maxim in the internal thread.
Is your feature request related to a problem? Please describe.
When executing many local activities in a row or parallel within a workflow task, (or a local activity is retrying), the workflow task is waiting until passed 80% of the workflow task timeout(10s). This could cause a big delay of query processing, or signal processing.
In certain scenarios, it's more flexible to let user workflow to decide when they can report the workflow task completed and then get(lease) a new workflow task to execute the next activities. This will then make it possible to process query task, or new signals.
Describe the solution you'd like
Additional context
Acknowledged by Maxim in the internal thread.