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

matthewb295 over 8 years ago

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...

Discussion posts and replies are publicly visible

Parents

0 matthewb295 over 8 years ago

Thanks, guys. One last similar question --- regarding the use of the 3 second timer, we found it eliminated a problem where the report smart service would fail to retrieve the lag/work time right after the task completed (basically, we theorized the analytics engines needed more time to cache the task data, and therefore provided an extra 3 seconds). We will definitely use queryprocessanalytics to obtain our data, but have you found that it takes a little bit of time before we can reliably retrieve task data, or have some info that brings any validity to our theory?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 matthewb295 over 8 years ago

Thanks, guys. One last similar question --- regarding the use of the 3 second timer, we found it eliminated a problem where the report smart service would fail to retrieve the lag/work time right after the task completed (basically, we theorized the analytics engines needed more time to cache the task data, and therefore provided an extra 3 seconds). We will definitely use queryprocessanalytics to obtain our data, but have you found that it takes a little bit of time before we can reliably retrieve task data, or have some info that brings any validity to our theory?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data