- Introduction
- Getting started
- Building with Maestro BPMN
- Understanding Maestro BPMN modeling
- Opening the modeling canvas
- Modeling your process
- Aligning and connecting BPMN elements
- Autopilot for Maestro (Preview)
- Process Repository
- Implementing a simple BPMN process
- Implementing a complex BPMN process
- Debugging
- Simulating
- Common implementation scenarios
- Building with Maestro Case
- Introduction to Maestro Case
- Maestro BPMN vs. Maestro Case: when to use case management
- The Maestro Case lifecycle: from event trigger to app experience
- Build your first case with Maestro Case
- Defining case keys (system vs. external)
- Establishing task I/O and write-back contracts
- Exit rules and early stage termination
- Modeling primary and secondary stages
- Triggering a case from Data Fabric
- Implementing stage-level personas and permissions
- Setting SLAs and automated escalation rules
- Configuring a rework loop (re-entry)
- Case Manager input and output contract
- Maestro Case component dictionary
- Building with Maestro Flow
- Integrations
- Operating
- Monitoring
- Optimizing
- Reference information
Flow incidents page capabilities for identifying, investigating, and resolving errors from configuration issues, runtime failures, and logic errors during flow execution.
The Flow incidents page helps you identify, investigate, and resolve errors that occur during flow execution. Incidents may result from configuration issues, missing connections, runtime failures, or logic errors in the flow. This view surfaces recent problems, their frequency, and the elements most likely to cause faults.
Flow incidents is in Preview. Behavior and available fields may change before general availability.
Use this page to:
- Pinpoint failed elements or misconfigured triggers.
- Track error trends over time.
- Investigate specific flows or elements prone to issues.
Key visualizations and metrics
- Incidents (chart) A time-series chart showing the number of faults per day. Use this to detect spikes or recurring instability.
- Top 10 processes with failures Bar chart listing flows with the highest number of faults. Helps prioritize debugging efforts.
- Top 10 faulted elements Lists specific flow elements (for example, send or service tasks) that triggered incidents. Each item links to the flow where the issue occurred.
Incident table columns
The incident table lists every flow 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 the Search, Flow, and Location filters to narrow results, and sort or filter the table by flow, location, or error type to access deeper logs for root-cause analysis.
| Field | Description |
|---|---|
| Flow name | The name of the flow where the incident occurred. |
| Location | The folder or workspace where the flow is stored. |
| Error message | A brief explanation of the failure. 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 flow. |