microsoft / microsoft/FastTrack

⚠️ Traffic data collection is failing

Open Beginner friendly
#482 60 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

traffic-collection-failure
Dominant language
HTML
Stars
224
Forks
129
Avg merge
1d 2h
Merged PRs (30d)
24

Description

The scheduled Collect Traffic Data workflow failed on 2026-07-22.

Traffic data has stopped being captured. Because GitHub only retains a rolling
14-day traffic window, every day this stays broken is data lost permanently.

Most likely cause: the TRAFFIC_TOKEN secret has expired or lost access.
The traffic API requires a PAT with push / administration:read on this repo — the
built-in GITHUB_TOKEN cannot read traffic.

Fix:

  1. Create a new PAT (classic repo scope, or fine-grained: Administration read + Contents R/W + Pull requests R/W).
  2. gh secret set TRAFFIC_TOKEN --repo microsoft/FastTrack --body "<NEW_PAT>"
  3. Re-run: gh workflow run traffic-stats.yml --repo microsoft/FastTrack

Failed run: https://github.com/microsoft/FastTrack/actions/runs/29897912067

This issue is opened automatically by the traffic workflow's failure alert. It will
be reused (not duplicated) while the label traffic-collection-failure stays open.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the failed traffic-stats.yml workflow run and verify that TRAFFIC_TOKEN has the required access. Set the replacement secret with gh secret set, then rerun traffic-stats.yml and confirm that traffic data collection succeeds.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions
Domain
ci-cd, devops
Issue type
Bug
Difficulty
1/5
Estimated time
Under an hour
Activity status
Active
Clarity
Clearly specified
Newbie friendliness
76/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.