MSE XXL-JOB generates events throughout the lifecycle of jobs, workflows, and alerts. Use the Event Hub to track execution history, diagnose scheduling failures, and audit alert activity.
View events
Log on to the MSE XXL-JOB console, and select a region in the top navigation bar.
In the left navigation bar, select .
Click the target instance.
In the left-side navigation pane, click Events.
The Event Hub organizes records into three tabs: job events, workflow events, and alert events.
Job events
Job events record the scheduling and execution lifecycle of individual jobs. If you run jobs on a frequent schedule, use this tab to locate a specific execution record and view its logs.
Event type | Description |
Scheduled | The job is queued for execution. |
Running | The job starts executing on a worker. |
Succeed | The job completed without errors. |
Failed | The job encountered an error during execution. |
Failing_Auto_Retry | A failed job is being retried automatically. |
Skip_Schedule | The scheduler skipped this scheduled run. This may be because the next scheduled time arrived before the previous run completed. |
Workflow events
Workflow events track the execution of workflows and individual node state transitions within a workflow.
Workflow-level events
Event type | Description |
workflow_scheduled | The workflow is queued for execution. |
workflow_waiting | The workflow is waiting. |
workflow_running | At least one node in the workflow is executing. |
workflow_hold | The workflow is suspended. |
workflow_succeed | All nodes completed successfully. |
workflow_failed | The workflow failed. No nodes are running, and at least one node has failed. |
Node-level events
Event type | Description |
node_dependent_pass | All upstream dependencies for the node are satisfied. |
external_dependent_pass | The external dependency check passed. |
node_branch_match | The branch condition evaluated to true for this node. |
node_skip | The node was skipped. This may be because the node is disabled, excluded by a calendar rule, or not matched by a logic branch. |
node_time_delay | Node execution is delayed. A start time is configured for the node, and that time has not arrived. |
Alert events
Alert events provide a historical record of job-level alerts. Use this tab to review past incidents, verify notification delivery, and identify recurring failure patterns.
Filter alert records by application, job name, time range, alert type, alert status, or notification channel.
Event retention
Retention periods vary by edition:
| Event category | Developer Edition | Professional Edition |
|---|---|---|
| Job events | 1 month | 2 months |
| Alert events | 1 month | 2 months |