Skip to content

Make daily dashboard refresh recover from delayed price feeds - #38

Merged
LEO0331 merged 20 commits into
mainfrom
fix/snapshot-targeted-recovery-alerts
Oct 14, 2026
Merged

LEO0331 merged 20 commits into
mainfrom
fix/snapshot-targeted-recovery-alerts

Conversation

@LEO0331

@LEO0331 LEO0331 commented Oct 14, 2026

Copy link
Copy Markdown
Owner

Context

The October 14 snapshot initially failed because all 20 ticker histories stopped at October 12 while the job required October 13; a later rerun succeeded. The strict readiness gate correctly prevented stale or incomplete data from publishing.

Recovery design

  • Preserve the 12:17 UTC daily refresh; add two bounded independent recovery windows at 15:17 and 18:17 UTC, each prices only.

  • Preflight checks the committed previous snapshot using the NYSE session and 60-row evidence criteria. If current, skip recovery without fetching or deploying.

  • Export price data only for tickers missing required coverage, with in-process retries narrowed further to failed tickers. Preserve last validated public snapshots on any failure.

  • Report missing tickers and categorized provider errors (session lag, timeout, access/rate-limit, other) in the GitHub Actions summary. Emit an Actions error annotation when the final scheduled retry remains blocked.

  • Public UI identifies published rather than continuously live data; after 96 hours mark the retained snapshot stale and flag Data Status attention.

Verification

New preflight tests, targeted price retry tests, provider diagnostics tests, workflow cron/DST contract tests, UI stale-snapshot regression tests. PR CI runs workflow, API and frontend tests.

Limits

Delayed GitHub schedules or persistent outages after the final retry still leave last-known-good dated data; alerts use GitHub Actions and repository notification settings.

@LEO0331
LEO0331 merged commit 4aae44c into main Oct 14, 2026
2 checks passed
@LEO0331
LEO0331 deleted the fix/snapshot-targeted-recovery-alerts branch October 14, 2026 06:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant