Use the SnapGPT Assistant to analyze a failed pipeline execution and receive an
AI-generated root cause analysis with suggested fixes.
Use the SnapGPT Analyze failed pipeline execution skill on the
Pipeline executions page in Monitor to analyze a failed pipeline
and get insight into the root cause of the failure with a prioritized list of suggested
fixes.
Note: SnapGPT must be enabled for your environment. Contact your Environment admin if SnapGPT
is not available.
-
In Monitor, click Pipeline executions in the left navigation
pane under Analyze.
-
In the Execution history table, locate the failed pipeline
execution and click its row to open the execution detail panel.
-
Open the SnapGPT panel using either of these methods:
- Click Ask SnapGPT in the execution detail panel.
- Click the SnapGPT button from the header panel.
-
Click Analyze failed pipeline execution. The panel begins
analyzing the failed execution. A loading indicator is displayed while the analysis is in
progress.
-
Review the analysis result in the SnapGPT panel.
The panel header shows a warning icon and the name of the pipeline being analyzed. The
result contains two sections:
-
Root cause: A concise headline describing the probable cause of the failure,
followed by a detailed explanation. Click the section header to collapse or expand it.
-
Suggested fixes: A prioritized list of recommended actions to resolve the
issue. Each fix card shows:
- A Recommended badge on the primary fix. This badge is
assigned to the fix that involves the smallest or safest code changes to prevent
that specific failure.
- A title and description of the fix.
- Where applicable, a code diff showing the change to make, with lines to remove
and lines to add clearly marked.
- An Open in Designer button. The button on the recommended
fix is filled, the buttons on the other fixes are outlined.
-
To further investigate and fix the issue in Designer, click Open in
Designer.
The SnapGPT panel remains open on the Monitor page with the analysis visible, so you
can refer to the suggested fix while working in Designer.