stackchain/stackchain-dashboard
1
0
Fork 0
Code Issues 9 Pull Requests 1 Actions Packages Projects Releases 713 Wiki Activity

Keep healthy live sections refreshing during partial outages #167

New Issue
Closed
opened 2026-08-07 04:48:31 +00:00 by rockachopa · 0 comments
rockachopa commented 2026-08-07 04:48:31 +00:00
Member
Copy Link

Problem

The pooled live endpoint collects context, activity, and notifications independently, but any one section failure starts a snapshot-wide cooldown. During a notification-only outage, otherwise healthy My Work and activity data stop refreshing. Retained notification arrays can also be presented as fresh by the mobile client even when their section is stale.

Product slice

Implement section-isolated refresh/backoff while preserving the single /api/v1/live request and single-flight behavior. Healthy due sections must continue refreshing; only a failing section observes exponential cooldown. Expose per-section freshness and render section-accurate status in the dashboard.

Acceptance tests

  • Repeated failure in one section backs off only that section while due healthy sections continue to refresh.
  • Concurrent callers coalesce eligible section refreshes into one live refresh task.
  • Retained failed-section data is marked stale with independent retry timing; successful recovery clears only that section's failure state.
  • Mobile My Work, activity, and Updates status use their own section metadata, not payload shape or one global flag.
  • Existing cancellation safety, notification invalidation, no-store behavior, and the full suite remain green.

Non-duplication evidence

Issue #149 added global outage cooldown and retained partial data; it did not isolate backoff by section. Issues #131 and #139 added unified polling and stale-while-revalidate. No open issue, open PR, release, or recent commit covers per-section refresh eligibility/freshness.

## Problem The pooled live endpoint collects context, activity, and notifications independently, but any one section failure starts a snapshot-wide cooldown. During a notification-only outage, otherwise healthy My Work and activity data stop refreshing. Retained notification arrays can also be presented as fresh by the mobile client even when their section is stale. ## Product slice Implement section-isolated refresh/backoff while preserving the single `/api/v1/live` request and single-flight behavior. Healthy due sections must continue refreshing; only a failing section observes exponential cooldown. Expose per-section freshness and render section-accurate status in the dashboard. ## Acceptance tests - Repeated failure in one section backs off only that section while due healthy sections continue to refresh. - Concurrent callers coalesce eligible section refreshes into one live refresh task. - Retained failed-section data is marked stale with independent retry timing; successful recovery clears only that section's failure state. - Mobile My Work, activity, and Updates status use their own section metadata, not payload shape or one global flag. - Existing cancellation safety, notification invalidation, no-store behavior, and the full suite remain green. ## Non-duplication evidence Issue #149 added global outage cooldown and retained partial data; it did not isolate backoff by section. Issues #131 and #139 added unified polling and stale-while-revalidate. No open issue, open PR, release, or recent commit covers per-section refresh eligibility/freshness.
timmy was assigned by rockachopa 2026-08-07 04:48:31 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
P0

Drop everything

  
P1

High priority

  
P2

Medium priority

  
agent:nightprowl

Assignments routed to the LongCat NightProwl evaluation worker

  
backend

Backend service

  
ci

Continuous integration / actions

  
frontend

Frontend / UI

  
meta

Meta / planning

  
pages

Gitea Pages

  
template

Repo template / standards

No Label
P0
P1
P2
agent:nightprowl
backend
ci
frontend
meta
pages
template
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
timmy
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: stackchain/stackchain-dashboard#167
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?