There is a use case where you may have a worker for external tasks that is processing tasks from many different camunda’s. Not sure on the exact usage at the moment, so opening this on the forum for ideas, but the core of it is the ability to have a external task worker to know which engine? instance? to send the data back to. So if the worker is querying different camunda’s it can know which one to send it back to. At the moment i am tracking this data as a mix of engine name, url, etc as part of a parent object that holds the actual FetchAndLock response. But would be great to have this type of data directly in the regular fetch and lock response so no parent object is needed.