I recently came across an unexpected behavior with task escalations. When attem

@bradc Hi, few months back even we came across the same situation and we used the following procedure in order to overcome this:

>> Send process id (in which task resides), task name (tp!display or tp!name) as message properties to the target process which has to be invoked upon escalation.

>> In the target process, query the process analytics with filters namely process id, task name (which are received from the process that contains task) and obtain the task id.

Once if you have task id, again you can query the process analytics and obtain the information associated with task.

I don't know how far the above solution is scalable in terms of best practices but let's see if any other practitioners comes with best approach.

This is the work around I had in mind, but I was hoping for a more straight forward solution.

Thank you for sharing.

Further you may tweak the above approach by making querying the process analytics and resolve the task id before hand while sending the task id as parameter (as the message parameters are expressionable) to target process.

Just to add more information to this, you're correct. Escalations, as part of the design of the product, have their own properties. Using tp!id will return the escalation ID not the task id. This is how the product was designed.

Hi Eduardo,

That was my assumption, thank you for confirming.