Source: Quick-sync-up-AgentZ call, 20 Jul 2026 (Atharva Shah, Murtaza Udaipurwala, Rahul Jadhav)
Suggested labels from the call: ux notifications p1
If you set up five workflows and walk away for a day, and one of them silently failed, or one MCP connection started erroring, or a credential expired, there is currently nothing that tells you. You'd only find out by opening each thing individually and checking its status.
The fix. Add a notification bell with a count badge in the header, covering the three cases that matter most: a scheduled workflow that failed while you were away, an MCP connection that's erroring, and a credential that expired.
Why it matters. Atharva summed up the actual user behavior here: "if the user creates five workflows, once he comes back we need to show him hey, one workflow failed." People aren't going to babysit a dashboard. They need the dashboard to flag them down instead.
Source:
Quick-sync-up-AgentZcall, 20 Jul 2026 (Atharva Shah, Murtaza Udaipurwala, Rahul Jadhav)Suggested labels from the call:
uxnotificationsp1If you set up five workflows and walk away for a day, and one of them silently failed, or one MCP connection started erroring, or a credential expired, there is currently nothing that tells you. You'd only find out by opening each thing individually and checking its status.
The fix. Add a notification bell with a count badge in the header, covering the three cases that matter most: a scheduled workflow that failed while you were away, an MCP connection that's erroring, and a credential that expired.
Why it matters. Atharva summed up the actual user behavior here: "if the user creates five workflows, once he comes back we need to show him hey, one workflow failed." People aren't going to babysit a dashboard. They need the dashboard to flag them down instead.