From 156a9ffd2346e33c21114c44c1299f0f761bdac9 Mon Sep 17 00:00:00 2001 From: SaelixCode Date: Thu, 7 May 2026 14:57:57 -0400 Subject: [PATCH] docs(stack-activity): wrap troubleshooting entries in Accordion blocks Match the foldable troubleshooting pattern established by docs/features/deploy-progress.mdx so the page stays compact and readers can scan to their issue. This is the canonical formatting for the /features section's troubleshooting blurbs going forward. --- docs/features/stack-activity.mdx | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/features/stack-activity.mdx b/docs/features/stack-activity.mdx index 16a04bda..afb93677 100644 --- a/docs/features/stack-activity.mdx +++ b/docs/features/stack-activity.mdx @@ -63,10 +63,10 @@ Sencho attributes every recorded event to the user who was authenticated when th ## Troubleshooting -### The Activity tab shows "No activity recorded yet" - + The activity log is populated by operations performed through Sencho on this stack: deploys, restarts, starts, stops, and image updates. Trigger one of those actions and the entry appears within a few seconds. + -### Operational events don't appear in the bell notification dropdown - + The notification dropdown surfaces system alerts and error-level events. User-initiated operational events (start, stop, restart, deploy, update) appear exclusively in the per-stack Activity tab, keeping the global tray focused on conditions that need your attention. +