- If there are 10 local activities in a workflow task and the task timeouts after local activity#5, will the workflow task persist the 5 completed activities (as MarkerRecord) before quitting?
The task doesn’t time out in this case. It is going to complete and open another one synchronously (aka workflow task heartbeat). The 5 completed are going to be recorded.
- Are there any drawbacks if the local activity (or a series of local activities) takes longer to complete than the workflow task timeout? Is it recommended to increase the workflow task timeout in such cases?
The task doesn’t timeout. It is extended through the heartbeat mechanism I described earlier. Note that it is intended for exceptional cases. Our recommendation is to use normal activities if you expect their execution to take longer than a few seconds.
I looked at my configuration and all the local activities have a timeout(StartToCloseTimeout) of 5 seconds. Is it possible that a local activity still gets stuck?
Yes, Java doesn’t support killing executing threads.
To be 100% sure, can I see the local activity configurations in the History tab of Web UI (I can see the configurations for workflow and normal activity, not for local activity).
No, I don’t think they are recorded.