Red-Cross Error Determination In Process Flow.

A red-cross error means the script task or smart service failed, something unexpected occurred.
In such case, the process pauses by exception.
Any process which has the status "Paused" is likely to be paused due to red-cross alert.
There maybe a few other reasons why a process gets paused other than red-cross alert..
But, in most cases whenever a process is paused, you can assume that it was due to red-cross alert

Yes chetan.. I will agree with you. when some unexpected error occurs, the status will be paused by exception. But, I observed..though the process node is failed by red-cross error, the status is active. In those cases, I need to filter those instances from the active status. I am looking for the solution for this.

@Anjup have u had a chance of looking this shared component
https://forum.appian.com/suite/tempo/records/item/lMBCLGOdlMUpdGVqW3dQaIKmclBmvvNEj8vu_cjb7T-5YiPr4Fu8ly5Yj1s09uenE4RYzA8zKyx7eiUhuimLnMWGJWMrIGgDWq7S8XvthJ9mnekvg/view/summary
, I don't used it but I think this will do your work

As a quick fix for something similar, we once implemented reports to show active instances with no active tasks (may not work depending on your process). It works well enough where we still reference the reports a few years later as a quick view to catch stalled requests.

One more way would be to create a portal report on the Process Model. Define a row called Active Instances and select # of Active instances from the process matrix. When you get the report ready, filter it by setting number of active tasks = 0. This would eventually lists all the process instances which are active still but do not have any active tasks, in other words, lists the errored processes.

@bollurumaheshsachina Hope this helps.. thanks

@raghunandanc could you please explain in-detail like what it means- 'select # of active instances from the process matrix'

@anjup: when you create a portal report and add a new field to it, you need to define what valule it takes. For that, if you + the Process Metrics, you will find a =num_active_tasks() which defines the number of active tasks for that model's running instances.

Attached screen shot for your ref..

Thanks @raghunandanc