Hi Russell,

We store information about Error tasks in our Data Warehouse and these can be reported on using the Custom Reporting module (using the Task Status dataset). We currently only store information about the number of Error tasks, rather than any details on why those tasks resulted in an Error state. We do however retain historical information about Error tasks so it is possible to report on the number of tasks with an active Error task, completed Error task, and so on.

I have included a simple example, below, showing how we can report on this dataset. In my example, I created a pivot table, filtering on the "Error" workflow task, counting the number of tasks by Project at the various task states. Note: I used the Project ID field in my example, for the purpose of anonymizing the data, but you could include a more easily identifiable field like the Project Name, Short Project ID, or Project Group Name.

We also store information about task duration, so you could go a step further than my example and report on pending or in-progress Error tasks with a duration of over 24 hours, for example.

You'll also notice I have used the new Custom Reporting module to prepare my example, as this provides support for pivot tables, which seemed like a good way of demonstrating this to you. The same data is available using the existing Custom Reporting module, but given we are due to meet to discuss the new module next week, my suggestion would be to wait until then unless you are under any time constraints for this request.

Cheers,

Ian

Hi Russell,

We store information about Error tasks in our Data Warehouse and these can be reported on using the Custom Reporting module (using the Task Status dataset). We currently only store information about the number of Error tasks, rather than any details on why those tasks resulted in an Error state. We do however retain historical information about Error tasks so it is possible to report on the number of tasks with an active Error task, completed Error task, and so on.

I have included a simple example, below, showing how we can report on this dataset. In my example, I created a pivot table, filtering on the "Error" workflow task, counting the number of tasks by Project at the various task states. Note: I used the Project ID field in my example, for the purpose of anonymizing the data, but you could include a more easily identifiable field like the Project Name, Short Project ID, or Project Group Name.

We also store information about task duration, so you could go a step further than my example and report on pending or in-progress Error tasks with a duration of over 24 hours, for example.

You'll also notice I have used the new Custom Reporting module to prepare my example, as this provides support for pivot tables, which seemed like a good way of demonstrating this to you. The same data is available using the existing Custom Reporting module, but given we are due to meet to discuss the new module next week, my suggestion would be to wait until then unless you are under any time constraints for this request.

Cheers,

Ian

Hi Ian,

Will the type of error ever be added to the data pool? It is helpful for us to understand if we are seeing a spike in certain types of errors so they can be investigated.

Thanks,

Russell

Following up on my question as this report as-is is not helpful enough for us to pinpoint error types.

Ian Parnell 

Follow up on this again as the report does not show error type. We are looking to be able to see the types of errors we had and when to pinpoint issues.