You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: cloud/portal/app-spicepod/deployments.md
+15-2Lines changed: 15 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -37,18 +37,31 @@ Issues are surfaced in four places:
37
37
38
38
* A banner on every page of the app, listing the most recent error and the number of other errors. The banner covers errors only — warnings appear in the **Issues** panel.
39
39
* An error count on the **Deployments** tab in the app navigation.
40
-
* An **Issues** panel on the **Deployments** page, listing every issue for the app, and on each instance page, scoped to that instance.
40
+
* An **Issues** panel on the **Deployments** page, and on each instance page scoped to that instance. Each panel lists up to five issues and links to the full list.
41
+
* A dedicated **Issues** page for the app, listing every issue without a limit.
41
42
* An indicator on the affected row in **Datasets** and **Models**, when an issue can be attributed to a component.
42
43
43
44
The feed combines runtime `ERROR` and `WARN` log lines with the reported status of each dataset. Repeats of the same failure collapse into one row with an occurrence count, so a connector retrying every second appears once rather than hundreds of times.
44
45
46
+
Issues are ordered errors first, then by how often they occurred, then by how recently. A panel capped at five rows therefore shows the errors before any warning, and the panel header keeps the full error and warning counts for the app or instance. **View all***N***issues** in the panel footer opens the dedicated **Issues** page, which lists the entire set.
47
+
45
48
Each row shows where the issue came from, how many times it occurred, when it was last seen, the dataset or model it was attributed to, and the instance that reported it. **Show details** expands the full text, including stack traces. The link on the row opens the originating instance's logs filtered to the issue, or the component's page for an issue reported by a dataset.
46
49
47
50
{% hint style="info" %}
48
51
Dismissing an error hides that specific error. A different failure raises the banner again.
49
52
{% endhint %}
50
53
51
-
An app with no issues shows no banner, no count, and no panel.
54
+
An app with no issues shows no banner, no count, and no panel. The dedicated **Issues** page remains reachable and reports that no issues were detected.
55
+
56
+
#### Get AI help
57
+
58
+
Each issue row has a **Get AI help** action that analyzes that issue on demand. The analysis reads the app's recent runtime logs and returns a likely root cause, a short numbered list of fix steps, links to the relevant documentation, and a confidence level.
59
+
60
+
Results are generated per issue and are not produced until the action is used.
61
+
62
+
{% hint style="warning" %}
63
+
An AI analysis is a suggestion, not a diagnosis. Verify each step against the app's own configuration before applying it.
0 commit comments