Error: rpc error: code = NotFound desc = Command 'UPDATE' rejected with code 'NOT_FOUND': Expected to update variables for element with key '2251799813701788', but no such element was found
It turns out zbctl expects the flow node instance key as a parameter. That only seems to be present in the operate rest api, but that does not seem to have any entrypoint using the task instance id give by the Tasklist REST API.
So, how do these two id/key generation concepts relate to each other and how can I infere the flow node instance key from the task instance id from the Tasklist REST API programmatically, to be able to add task instance variables using zbctl?
Also, I assume SetVariablesCommand from the Java API also requires the flow instance key as I see it in Operate and not the task instance id as reported by the Tasklist REST API, correct?
Hi @PKAndre, welcome to the forums! The id in the Tasklist search query is the ID of the task itself. The same response should also include a processInstanceKey, which is a reference to the process instance ID associated with that task. I believe you should be able to use the process instance ID with zbctl
thank you for looking into this. You are probably right with your suggestion, that it would create a variable in the process instance. But I do not want to create a process instance variable, instead I want to create a variable that is explicitly one local to the task. And for this, as of my understanding, I need the flow node instance key of the task, which I currently cannot infer from the task instance id I get from the tasklist REST api.