Hi All, Is there any process model property that will show when the p

There is not property. You can configure the process to alert a group(s) when there's is a error.

@ Shyamb Yes it is there.But we want to know if process have failed through a variable or some process model properties to warn upcoming processes about failure.

You can check if it's paused by exception using pp.status (in a record) or process_status() (in a portal report). There are four states of the status:active=0, completed=1, paused=2, cancelled=3, paused by exception=4. Paused by exception indicates there is an error.

forum.appian.com/.../Handling_Process_Exceptions.html

@mohamedt808 There is no automatic trigger. What is your requirement?

If there is any particular flow or smart node which you need to monitor or escalate in case of process failures, you can wrap that particular module in a separate sub process and then configure exception on the sub process node in your parent process to set the timer set to max time. In case of failure the exception path would trigger thereafter which you can set your process variables as required.

PS: The above approach is just one of the hack to achieve such cases which might or might not fit for all use cases (such as if there are any user input tasks in that sub process, etc)

It would be nice if soft/transient (vs hard/non recoverable) errors could be programmatically caught and allow the model designer/developer to control message and next action (i.e. redo a task). With increased modeling capabilities in Appian, designers/modelers need more support such as these to design processes that wouldn't unnecessarily pause because of minor errors. Kind of like a catch/throw in Java. -- My two cents.

I think a retry capability and better handling of exceptions (particularly transient database connectivity ones) would be helpful. Likewise, the database query smart service that lets you directly perform an SQL statement has a 'pause on error' attribute you can set to true/false and then capture the error in a pv variable. Nothing like this exists for other smart services. Sadly, except for Alerts which we have to monitor throughout the day, there isn't an easy way to handle sporadic connectivity problems. We end up having to restart nodes periodically.