Update workflow status in place without a page reload

[7174Andy]

Problem

Schedule status only updated on a manual browser reload. Watching a dispatched run meant hitting refresh over and over.

Approach

Poll getSchedules() every 10s while any schedule is non-terminal — pending, processing, or triggered with no conclusion yet. When everything has settled, no timer starts and no requests are issued.

10s is deliberate, not arbitrary: the cron tick that writes these rows runs once a minute, so the badge is at most ~70s behind the real GitHub run regardless. Polling faster buys nothing.

Adds a Refresh button, and an updating… indicator beside the Pending and History headers that shows for the background poll as well as the manual click.

Details worth a look in review

• fetchSchedules holds the in-flight promise, not a boolean. Overlapping calls collapse onto one request, so a slow response can't land after a newer one and repaint running… over an already-resolved succeeded. A click racing the poll timer still awaits a real result rather than no-op'ing.
• 400ms floor on the indicator. A schedule read finishes well under 100ms, so without it the indicator flashes for a single frame every poll — jitter, not feedback. Data still renders the moment it arrives.
• The indicator is aria-hidden. It repeats every 10s; a live region announcing it that often would bury the badge change that actually matters. Happy to reverse this if you'd rather it announce.
• The Refresh button is not disabled while fetching. The promise dedupe already collapses concurrent clicks, and disabling it would grey the button out every 10s on its own.

Trade-off

A tab left open with a schedule days out polls every 10s the whole time. An earlier version slept until the schedule came due, but that cost ~77 lines (a helper module, a now state, a two-branch timer) to optimise a case that only bites if you leave a tab open for days. Cut it deliberately.

Testing

npx tsc --noEmit clean, npx eslint . clean, npx vitest run 84 passing.

No automated coverage for the polling itself — it's useEffect timer behavior with no test harness for components in this repo (vitest runs in node, no DOM). Verified by hand in the running dev app.

🤖 Generated with Claude Code

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
gitcron	Ready	Preview	Aug 2, 2026 2:28am