Hello Community,
We are currently facing challenges with early detection of errors in Appian processes.
In our implementation, many flows include killers and orchestrate multiple subprocesses. While Appian’s process monitor allows us to see execution paths and variable values, this visibility is very limited once the processes are archived. As a result, identifying failures in a timely manner is difficult, especially in complex orchestrator flows.
What we are looking for is:
Early Alerts
Is there a way to configure alerts/notifications when:
A process fails,
A process takes longer than expected,
A subprocess does not start or complete as designed?
Observability / Logging
Are there recommended best practices or design patterns to achieve better observability?
For example: persisting process variables, execution history, and error details (including history errors and variable values) into logs or records so we can analyze issues even after processes are archived.
Orchestrators and Subprocesses
In orchestrator → subprocess scenarios, how can we get consolidated information (status, PVs, errors) from all subprocesses so that the orchestrator has a clear view of the overall health of execution?
Our goal is to detect issues at an early stage and provide support teams with actionable logs that contain enough metadata (PVs, history, errors, timings, etc.) to troubleshoot effectively.
Any guidance, patterns, or product features that you have successfully used for proactive monitoring and alerting would be greatly appreciated.
Thanks in advance! Roddy
Discussion posts and replies are publicly visible