feat(connected-accounts): show expiry/inactive reason in status column

@zen-agentchecks n/achecks…zen/show-connection-expiry-reason-7ngzja → main1 files · +31 −7updated 1mo ago

▸Description · 1 noise

Description

Restore the "why is this connection expired?" affordance from the old dashboard.

The connected accounts table currently shows just a status badge (Expired / Failed / Inactive) — the user has no way to tell whether the token expired, was revoked, hit max auth failures, was disabled by a user, etc., without clicking into the user detail panel. The old dashboard surfaced this directly on the Manage Auth Config view via a hover tooltip on the status badge.

This PR adds the same affordance: an Info icon next to the status badge that shows the API's status_reason on hover (e.g. "Access token expired, and no refresh token available.", "Max auth failures reached", "Auth config is disabled").

The data was already plumbed end-to-end — listConnectedAccounts.ts selects statusReason from Postgres and returns it on each item — but the table wasn't rendering it. One change to the shared connected-accounts-columns.tsx surfaces it everywhere ConnectedAccountsTable is used:

Project-level connected accounts list
Auth config detail page (the equivalent of the old "Manage Auth Config" view)
User detail "Connected accounts" tab
Auth config + user preview panels

Icon is hidden when statusReason is null (i.e. healthy ACTIVE connections), so the column stays visually quiet for the happy path. onClick stops propagation so hovering the icon doesn't trigger row-click navigation.

How did I test this PR

pnpm exec tsgo --noEmit -p tsconfig.json — clean (exit 0)
pnpm lint on the modified file — no new lint errors (the 5 pre-existing oxlint errors are in warp-tunnel/ and one tracked-Button rule, unrelated)
Codex review — no findings: "The change is limited to rendering an existing statusReason field in the connected accounts status cell, and typechecking passes. I did not find any discrete correctness issue introduced by the patch."
CI: tsgo typecheck ✅ green; Vercel preview ✅ deployed
End-to-end browser verification on Vercel preview — logged in as the test user, navigated to Auth Configs → Outlook auth config detail panel → hovered the new (i) icon on an expired connection. Tooltip shows the real reason: "Connection initiation did not complete within 10 minutes"

Visual proof

Screenshot (tooltip open): tooltip

Video walkthrough: https://pub-b70cb36a6853407fa468c5d6dec16633.r2.dev/260902/generic/file_upload/request/84f9f04bb3401489a2952d4838cd0780

Triggered by: uday@composio.dev | Source: slack Session: https://zen-api-production-4c98.up.railway.app/dashboard/#/chat/zen-b27cbae2d3aa

▸ 1 bot/status comment hidden

@vercel[bot]1mo ago

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
dashboard	Ready	Preview, Comment	May 2, 2026 10:02am

loading diff…