- Introduction
- Getting started
- Process modeling
- Process implementation
- Process operations
- Process monitoring
- Process optimization
- Reference information
Maestro user guide
Process incidents
The Process incidents page helps you identify, investigate, and resolve errors that occur during process execution. Incidents may result from configuration issues, missing connections, runtime failures, or logic errors in the process model. This view surfaces recent problems, their frequency, and the elements most likely to cause faults.
Use this page to:
- Pinpoint failed tasks or misconfigured gateways.
- Track error trends over time.
- Investigate specific processes or elements prone to issues.
The following diagram shows how Maestro handles process incidents. It outlines how incidents are detected and classified, and how users track progress to ensure process continuity.
Key visualizations and metrics
- **Incidents over time (chart)**A time-series chart showing the number of faults per day. Use this to detect spikes or recurring instability.
- Top 10 processes with failuresBar chart listing processes with the highest number of faults. Helps prioritize debugging efforts.
- Top 10 faulted elementsLists specific BPMN elements (e.g., tasks or gateways) that triggered incidents. Each item links to the process model where the issue occurred.
Incident table columns
The incident table lists every process execution that encountered an error, along with key details to help you identify patterns and troubleshoot faster. Each column provides context about where and when the issue occurred, how often it appeared, and what type of failure was detected. Use this table to filter or sort incidents by process, location, or error type and to access deeper logs for root-cause analysis.
| Field | Description |
|---|---|
| Process name | The name of the process where the incident occurred. |
| Location | The folder or workspace where the process is stored. |
| Error message | A brief explanation of the failure (e.g., “No outgoing flow for gateway”). Each message links to more detail if available. |
| Count | How many times the same error was encountered. |
| First seen | When the issue was first detected in this process. |
Example errors
-
No outgoing flow for gateway
A decision point (gateway) in the process does not have a valid sequence flow when the process reaches it.
-
Failure to start the Orchestrator RPA job
Indicates the process tried to start an RPA job, but it failed—possibly due to missing permissions or robot availability.
