- Einleitung
- Erste Schritte
- Voraussetzungen
- Unterstützte Sicherheitsstandards
- Choosing a Maestro canvas
- Ways to build with Maestro
- Maestro in Playground ausprobieren (Vorschau)
- Startseite
- BPMN instances
- BPMN incidents
- Fall-App
- Case instances
- Fallvorfälle
- Flow instances (Preview)
- Flow incidents (Preview)
- Maestro-Prozesse testen
- Tastenkombinationen
- Building with Maestro BPMN
- Understanding Maestro BPMN modeling
- Öffnen der Modellierungsarbeitsfläche
- Modellierung Ihres Prozesses
- Ausrichten und Verbinden von BPMN-Elementen
- Autopilot for Maestro (Vorschau)
- Prozess-Repository
- Implementing a simple BPMN process
- Implementing a complex BPMN process
- Debugging
- Simulieren
- Häufige Implementierungsszenarien
- Building with Maestro Case
- Einführung in Maestro Case
- Maestro BPMN vs. Maestro Case: Wann wird Case Management verwendet?
- Der Lebenszyklus von Maestro Case: Vom Ereignis-Trigger zum App-Erlebnis
- Build your first case with Maestro Case
- Definieren von Fallschlüsseln (System vs. extern)
- Erstellen von Task-E/A- und Write-Back-Verträgen
- Austrittsregeln und Beendigung der frühen Phase
- Modellieren von primären und sekundären Phasen
- Auslösen eines Falls aus Data Fabric
- Implementieren von Personas und Berechtigungen auf Phasenebene
- Festlegen von SLAs und automatisierten Eskalationsregeln
- Konfigurieren einer Nacharbeitsschleife (Wiedereintritt)
- Eingabe- und Ausgabevertrag für den Fall Manager
- Maestro Case component dictionary
- Building with Maestro Flow
- Integrationen
- Operating
- Überwachung
- Optimizing
- Referenzinformationen
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.
Über diese Seite können Sie:
- Pinpoint failed elements or misconfigured triggers.
- Fehlertrends im Zeitverlauf nachverfolgen.
- Investigate specific flows or elements prone to issues.
Wichtige Visualisierungen und Metriken
- 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.
Spalten der Vorfallstabelle
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.
| Feld | Beschreibung |
|---|---|
| Flow name | The name of the flow where the incident occurred. |
| Ort | The folder or workspace where the flow is stored. |
| Fehlermeldung | A brief explanation of the failure. Each message links to more detail if available. |
| Anzahl | Wie oft der gleiche Fehler aufgetreten ist. |
| Zuerst gesehen | When the issue was first detected in this flow. |