We have a "taskMetrics" SQL table for our applications that contains d

We have a "taskMetrics" SQL table for our applications that contains data for the "lag()" and "work()" expressions related to a task. We have found that the we need to retrieve the lag/work time for a task by running a Execute Process Report smart service node (since we cannot simply save these times in the task outputs), but have encountered some instances where the lag/work time aren't returned by the Execute Process Report node if it is implemented in a process flow directly after the task node. Adding a slight delay (3 seconds seems to work) allows the lag/work time can be consistently retrieved, but this sometimes causes issues when we would like to chain through the task write (for storing the created primary key from our taskMetrics table in a chained task in the process, for example).

My question is this: is there a way to guarantee that lag/work time can be queried for a task after it is complete? We are going to start using queryprocessan...

OriginalPostID-217691

OriginalPostID-217691