Case incidents

Case incidents page capabilities for identifying, investigating, and resolving errors from configuration issues, runtime failures, and logic errors during case execution.

The Case incidents page helps you identify, investigate, and resolve errors that occur during case execution. Incidents may result from configuration issues, missing connections, runtime failures, or logic errors in the case plan. This view surfaces recent problems, their frequency, and the tasks and stages most likely to cause faults.

Use this page to:

• Pinpoint failed tasks or misconfigured stage transitions.
• Track error trends over time.
• Investigate specific cases or stages prone to issues.

The following diagram shows how Maestro handles case incidents. It outlines how incidents are detected and classified, and how users track progress to ensure case 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 cases with failures Bar chart listing cases with the highest number of faults. Helps prioritize debugging efforts.
• Top 10 faulted stages or tasks Lists specific case stages or tasks that triggered incidents. Each item links to the case plan where the issue occurred.

Incident table columns

The incident table lists every case 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 case, location, or error type and to access deeper logs for root-cause analysis.

Field	Description
Case name	The name of the case where the incident occurred.
Location	The folder or workspace where the case 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 case.