- Introducción
- Primeros pasos
- Building with Maestro BPMN
- Understanding Maestro BPMN modeling
- Abrir el lienzo de modelado
- Modelar tu proceso
- Alinear y conectar elementos BPMN
- Autopilot para Maestro (vista previa)
- Repositorio de procesos
- Implementing a simple BPMN process
- Implementing a complex BPMN process
- Depuración
- Simular
- Escenarios de implementación comunes
- Building with Maestro Case
- Introducción a Maestro Case
- Maestro BPMN frente a Maestro Case: cuándo utilizar la gestión de casos
- El ciclo de vida de Maestro Case: del desencadenador de eventos a la experiencia de la aplicación
- Build your first case with Maestro Case
- Definir claves de caso (de sistema o externo)
- Establecer contratos de entrada/salida y de escritura diferida de tareas
- Reglas de salida y terminación temprana de etapas
- Modelar las etapas principal y secundaria
- Iniciar un caso desde Data Fabric
- Implementar perfiles y permisos a nivel de etapa
- Establecer SLA y reglas de escalado automatizadas
- Configurar un bucle de reprocesamiento (reingreso)
- Contrato de entrada y salida del gestor de casos
- Maestro Case component dictionary
- Building with Maestro Flow
- Integraciones
- Operating
- Supervisión
- Optimizing
- Información de referencia
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.
Usa esta página para:
- Pinpoint failed tasks or misconfigured stage transitions.
- Realiza un seguimiento de las tendencias de error a lo largo del tiempo.
- 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.
Visualizaciones y métricas clave
- Incidentes a lo largo del tiempo (gráfico) Un gráfico de serie temporal que muestra el número de fallos por día. Utilízalo para detectar picos o inestabilidad recurrente.
- 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.
Columnas de tabla de incidentes
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.
| Campo | Descripción |
|---|---|
| Case name | The name of the case where the incident occurred. |
| Ubicación | The folder or workspace where the case is stored. |
| Mensaje de error | A brief explanation of the failure. Each message links to more detail if available. |
| Recuento | Cuántas veces se encontró el mismo error. |
| Vistos en primer lugar | When the issue was first detected in this case. |