Greetings. Was wondering if I could validate something.
Java SDK, v1.24.2. I have a workflow that looks something like:
@WorkflowMethod(name = "Lock")
void execute(int maxNumLockHolders, Map<String, String> objectRunIdMap);
@UpdateMethod
boolean obtainLock(LockRequest lockRequest);
At the time this was coded (July '24) I wasn’t aware of any batch capability for @UpdateMethod. Therefore, we coded to (i) start workflow and then (ii) call the update. A little messy, but it appeared to work.
I would expect that everytime obtainLock is called, execute would have been called first. However, this is not always the case. Sometimes, I witness obtainLock being called first. I can prove this by simply putting log messages into the class’s constructor, etc. I am fairly certain this is a bug, but I’m not positive.
Moving on . . . I have been scanning release notes for SDKs v1.26.x and v1.27.x. Specifically, support for WorkflowClient.startUpdateWithStart) (formerly WorkflowClient.updateWithStart). This looks exactly like what I need.
I’m thinking that I’ve found a bug, but that it was likely fixed in subsequent releases, that sound right?
Thank you!