fix: increase claude-token-usage-analyzer timeout to 45 minutes#1842
Merged
Conversation
The workflow was timing out at 15 minutes while still downloading artifacts. The agent needs more time to list workflow runs, download token-usage.jsonl artifacts, and compile the analysis report. Fixes #1838 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
✅ Coverage Check PassedOverall Coverage
📁 Per-file Coverage Changes (1 files)
Coverage comparison generated by |
Contributor
There was a problem hiding this comment.
Pull request overview
This PR aims to prevent the “Daily Claude Token Usage Analyzer” agentic workflow from timing out by increasing the configured timeout from 15 to 45 minutes.
Changes:
- Increase
timeout-minutesto 45 in the source workflow definition. - Regenerate the compiled workflow (
*.lock.yml) so the agent execution step uses the longer timeout. - Update the actions lockfile to include a new
github/gh-aw-actions/setup@v0.67.3entry (via regeneration).
Show a summary per file
| File | Description |
|---|---|
| .github/workflows/claude-token-usage-analyzer.md | Bumps timeout-minutes to 45 in the workflow frontmatter. |
| .github/workflows/claude-token-usage-analyzer.lock.yml | Reflects the new timeout, but also includes additional regenerated changes (compiler/version/schedule/tool pinning). |
| .github/aw/actions-lock.json | Adds an entry for github/gh-aw-actions/setup@v0.67.3 due to the regenerated lock workflow. |
Copilot's findings
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Comments suppressed due to low confidence (2)
.github/workflows/claude-token-usage-analyzer.lock.yml:49
- This change shifts the scheduled cron time ("17 12" → "48 19"). The PR description only mentions increasing the timeout; if the schedule change is unintended, pin an explicit cron in the source .md (instead of relying on the compiler’s "daily (scattered)" time) or recompile without altering the schedule output.
schedule:
- cron: "48 19 * * *"
# Friendly format: daily (scattered)
.github/workflows/claude-token-usage-analyzer.lock.yml:358
- This regeneration pins GitHub Copilot CLI to 1.0.21 and bumps AWF to v0.25.16. Other workflows in this repo currently install Copilot CLI as
latestand use the previous AWF version, so this introduces an unadvertised behavioral change beyond the timeout update; either keep these consistent with the rest of the workflows or update the PR scope/description accordingly.
- name: Install GitHub Copilot CLI
run: ${RUNNER_TEMP}/gh-aw/actions/install_copilot_cli.sh 1.0.21
env:
GH_HOST: github.com
- name: Install AWF binary
run: bash ${RUNNER_TEMP}/gh-aw/actions/install_awf_binary.sh v0.25.16
- name: Determine automatic lockdown mode for GitHub MCP Server
- Files reviewed: 3/3 changed files
- Comments generated: 2
Comment on lines
+1
to
+2
| # gh-aw-metadata: {"schema_version":"v3","frontmatter_hash":"050995a1e51e6fb4c47feea8c91a3c9d39a180db586fdc519ded957b64e97b67","compiler_version":"v0.67.3","strict":true,"agent_id":"copilot"} | ||
| # gh-aw-manifest: {"version":1,"secrets":["COPILOT_GITHUB_TOKEN","GH_AW_GITHUB_MCP_SERVER_TOKEN","GH_AW_GITHUB_TOKEN","GITHUB_TOKEN"],"actions":[{"repo":"actions/checkout","sha":"de0fac2e4500dabe0009e67214ff5f5447ce83dd","version":"v6.0.2"},{"repo":"actions/download-artifact","sha":"3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c","version":"v8.0.1"},{"repo":"actions/github-script","sha":"ed597411d8f924073f98dfc5c65a23a2325f34cd","version":"v8"},{"repo":"actions/upload-artifact","sha":"bbbca2ddaa5d8feaa63e36b76fdaad77386f024f","version":"v7"},{"repo":"github/gh-aw-actions/setup","sha":"eef369c24101e76a5bf51579c26798b28f666813","version":"v0.67.3"}]} |
There was a problem hiding this comment.
The workflow lock file was regenerated with gh-aw v0.67.3 (metadata/compiler_version), while the rest of the repo’s workflow lock files are still on v0.67.2. If this PR’s intent is only the timeout bump, consider recompiling with the repo’s current compiler version to avoid pulling in unrelated lockfile churn (dependency/version/behavior changes).
This issue also appears in the following locations of the same file:
- line 47
- line 352
Comment on lines
+43
to
+47
| "github/gh-aw-actions/setup@v0.67.3": { | ||
| "repo": "github/gh-aw-actions/setup", | ||
| "version": "v0.67.3", | ||
| "sha": "eef369c24101e76a5bf51579c26798b28f666813" | ||
| }, |
There was a problem hiding this comment.
This adds a new global action-lock entry for github/gh-aw-actions/setup@v0.67.3. If the intent of the PR is only to increase the workflow timeout, consider avoiding a setup action/version bump (or upgrading the repo consistently) to prevent lockfile drift and unrelated changes.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Daily Claude Token Usage Analyzer workflow was timing out at 15 minutes (#1838). The agent spends significant time listing workflow runs, downloading
token-usage.jsonlartifacts from each run, and compiling the analysis — 15 minutes isn't enough.Increases
timeout-minutesfrom 15 to 45.Fixes #1838