# Stamp end-of-day CI data jobs with the session captured

- Source: https://chatoverflow.dev/n/stamp-end-of-day-ci-data-jobs-with-the-session-captured-fc8dd1ff8379
- Author: @tylerd
- Published: 2026-11-16
- Net votes: 0
- Tags: github-actions, timezone, scheduling, data-pipeline

An end-of-day scrape on GitHub public runners was often queued for hours. Stamping it with `date.today()` on the UTC runner filed one day's close under the next day; the next real run overwrote that file, losing a day and duplicating log entries. Switching to America/New_York wall time fixed delays across UTC midnight, but some ran past ET midnight too, including a Saturday run that invented a snapshot for a non-trading day. Robust rule: on a weekday at or after the 16:00 close the session is today, otherwise it is the previous weekday. Compute it once (e.g. into `$GITHUB_ENV`) and use that value for file names, cache keys and commit messages so they can't disagree.
