Repository navigation
[aw] [aw] Failure Investigator (6h) exceeded daily AI credits budget #66699
Description
Workflow Failure
Workflow: [aw] Failure Investigator (6h)
Branch: main
Run: https://github.com/github/gh-aw/actions/runs/37697192984
Warning
Daily Workflow AIC Guardrail Exceeded: The agent was not started because the 24-hour guardrail total reached the configured AI Credits threshold.
- 24h AIC guardrail total:
10.4KAI Credits - Recorded AIC:
1.4KAI Credits - Estimated AIC (unresolved accounting):
9KAI Credits - Configured threshold:
10KAI Credits
Estimated credits represent conservative per-run maximums where accounting is unavailable, not confirmed consumption. Subsequent scans retry unresolved accounting and replace estimates if recorded usage becomes available. Otherwise, these estimates stop counting when the affected runs leave the rolling 24-hour window.
Recorded AIC values are approximate; estimates are not measured consumption. Consult the billing dashboards for accurate usage and charges.
How to raise the daily limit
Set max-daily-ai-credits in your workflow frontmatter to a higher value, then recompile:
max-daily-ai-credits: 20KCommon suffix shorthands: K = thousands, M = millions (e.g. 2M = 2,000,000).
After editing the workflow source file, regenerate the compiled lock file:
gh aw compileCommit and push the updated .lock.yml file.
[!NOTE]
Raising the limit increases the number of AI inference calls the workflow can make
per 24-hour window. Review your Copilot or model provider billing
before significantly increasing the threshold (for example, before doubling the current
value or setting it far above expected usage).
What is the daily AI Credits guardrail?
The max-daily-ai-credits frontmatter option sets a per-workflow spending cap measured in AI Credits across the 24-hour window before the current run. The cap is scoped to the repository and workflow — it aggregates usage across all runs of this workflow regardless of who triggered them.
When the total of recorded AI Credits and unresolved conservative estimates across all completed runs of this workflow in the last 24 hours reaches the threshold, the activation job sets the daily_ai_credits_exceeded output to true and the agent job is skipped for that run. The conclusion job still runs and creates this report.
The guardrail is evaluated at activation time, not retrospectively, so a single very large run that pushes usage over the threshold only blocks subsequent runs in the same window — it does not cancel a run that is already in progress.
How to disable this guardrail
[!CAUTION]
Disabling this guardrail removes the per-workflow spending cap. Only disable it if you have
an alternative mechanism for controlling AI cost usage or if the workflow is intentionally
uncapped.
Set max-daily-ai-credits: -1 in the workflow frontmatter to explicitly disable the guardrail, then recompile:
max-daily-ai-credits: -1gh aw compileAlternatively, remove the max-daily-ai-credits key entirely to fall back to the enterprise-wide default (if one is configured) or to run with no per-workflow cap.
Action Required
Assign this issue to an agent to debug and fix the issue.
Optimize token consumption
This failure was triggered by a guardrail limit (max-daily-ai-credits). Use this prompt with any coding agent (GitHub Copilot, Claude, Gemini, etc.) to analyze token usage and reduce costs:
Optimize the agentic workflow token consumption using https://raw.githubusercontent.com/github/gh-aw/main/optimize.md
The workflow run is at https://github.com/github/gh-aw/actions/runs/37697192984
Debug with any coding agent
Use this prompt with any coding agent (GitHub Copilot, Claude, Gemini, etc.):
Debug the agentic workflow failure using https://raw.githubusercontent.com/github/gh-aw/main/debug.md
The failed workflow run is at https://github.com/github/gh-aw/actions/runs/37697192984
Manually invoke the agent
Debug this workflow failure using your favorite Agent CLI and the agentic-workflows prompt.
- Start your agent
- Load the
agentic-workflowsskill from.github/skills/agentic-workflows/SKILL.mdor https://github.com/github/gh-aw/blob/main/.github/skills/agentic-workflows/SKILL.md - Type
debug the agentic workflow aw-failure-investigator failure in https://github.com/github/gh-aw/actions/runs/37697192984
Tip
Stop reporting this workflow as a failure
To stop a workflow from creating failure issues, set report-failure-as-issue: false in its frontmatter:
safe-outputs:
report-failure-as-issue: falseGenerated from [aw] Failure Investigator (6h) · ◷
- expires on Oct 8, 2026, 10:39 AM UTC
Activity
github-actions commentedon Oct 8, 2026
Agent job 37733358315 failed.
Warning
Daily Workflow AIC Guardrail Exceeded: The agent was not started because the 24-hour guardrail total reached the configured AI Credits threshold.
10.9KAI Credits854AI Credits10KAI Credits10KAI CreditsEstimated credits represent conservative per-run maximums where accounting is unavailable, not confirmed consumption. Subsequent scans retry unresolved accounting and replace estimates if recorded usage becomes available. Otherwise, these estimates stop counting when the affected runs leave the rolling 24-hour window.
Recorded AIC values are approximate; estimates are not measured consumption. Consult the billing dashboards for accurate usage and charges.
How to raise the daily limit
Set
max-daily-ai-creditsin your workflow frontmatter to a higher value, then recompile:Common suffix shorthands:
K= thousands,M= millions (e.g.2M= 2,000,000).After editing the workflow source file, regenerate the compiled lock file:
Commit and push the updated
.lock.ymlfile.What is the daily AI Credits guardrail?
The
max-daily-ai-creditsfrontmatter option sets a per-workflow spending cap measured in AI Credits across the 24-hour window before the current run. The cap is scoped to the repository and workflow — it aggregates usage across all runs of this workflow regardless of who triggered them.When the total of recorded AI Credits and unresolved conservative estimates across all completed runs of this workflow in the last 24 hours reaches the threshold, the activation job sets the
daily_ai_credits_exceededoutput totrueand the agent job is skipped for that run. The conclusion job still runs and creates this report.The guardrail is evaluated at activation time, not retrospectively, so a single very large run that pushes usage over the threshold only blocks subsequent runs in the same window — it does not cancel a run that is already in progress.
How to disable this guardrail
Set
max-daily-ai-credits: -1in the workflow frontmatter to explicitly disable the guardrail, then recompile:Alternatively, remove the
max-daily-ai-creditskey entirely to fall back to the enterprise-wide default (if one is configured) or to run with no per-workflow cap.github-actions commentedon Oct 8, 2026
Agent job 37735756351 failed.
Warning
Daily Workflow AIC Guardrail Exceeded: The agent was not started because the 24-hour guardrail total reached the configured AI Credits threshold.
10.8KAI Credits814AI Credits10KAI Credits10KAI CreditsEstimated credits represent conservative per-run maximums where accounting is unavailable, not confirmed consumption. Subsequent scans retry unresolved accounting and replace estimates if recorded usage becomes available. Otherwise, these estimates stop counting when the affected runs leave the rolling 24-hour window.
Recorded AIC values are approximate; estimates are not measured consumption. Consult the billing dashboards for accurate usage and charges.
How to raise the daily limit
Set
max-daily-ai-creditsin your workflow frontmatter to a higher value, then recompile:Common suffix shorthands:
K= thousands,M= millions (e.g.2M= 2,000,000).After editing the workflow source file, regenerate the compiled lock file:
Commit and push the updated
.lock.ymlfile.What is the daily AI Credits guardrail?
The
max-daily-ai-creditsfrontmatter option sets a per-workflow spending cap measured in AI Credits across the 24-hour window before the current run. The cap is scoped to the repository and workflow — it aggregates usage across all runs of this workflow regardless of who triggered them.When the total of recorded AI Credits and unresolved conservative estimates across all completed runs of this workflow in the last 24 hours reaches the threshold, the activation job sets the
daily_ai_credits_exceededoutput totrueand the agent job is skipped for that run. The conclusion job still runs and creates this report.The guardrail is evaluated at activation time, not retrospectively, so a single very large run that pushes usage over the threshold only blocks subsequent runs in the same window — it does not cancel a run that is already in progress.
How to disable this guardrail
Set
max-daily-ai-credits: -1in the workflow frontmatter to explicitly disable the guardrail, then recompile:Alternatively, remove the
max-daily-ai-creditskey entirely to fall back to the enterprise-wide default (if one is configured) or to run with no per-workflow cap.github-actions commentedon Oct 8, 2026
Agent job 37740306184 failed.
Warning
Daily Workflow AIC Guardrail Exceeded: The agent was not started because the 24-hour guardrail total reached the configured AI Credits threshold.
10.8KAI Credits774AI Credits10KAI Credits10KAI CreditsEstimated credits represent conservative per-run maximums where accounting is unavailable, not confirmed consumption. Subsequent scans retry unresolved accounting and replace estimates if recorded usage becomes available. Otherwise, these estimates stop counting when the affected runs leave the rolling 24-hour window.
Recorded AIC values are approximate; estimates are not measured consumption. Consult the billing dashboards for accurate usage and charges.
How to raise the daily limit
Set
max-daily-ai-creditsin your workflow frontmatter to a higher value, then recompile:Common suffix shorthands:
K= thousands,M= millions (e.g.2M= 2,000,000).After editing the workflow source file, regenerate the compiled lock file:
Commit and push the updated
.lock.ymlfile.What is the daily AI Credits guardrail?
The
max-daily-ai-creditsfrontmatter option sets a per-workflow spending cap measured in AI Credits across the 24-hour window before the current run. The cap is scoped to the repository and workflow — it aggregates usage across all runs of this workflow regardless of who triggered them.When the total of recorded AI Credits and unresolved conservative estimates across all completed runs of this workflow in the last 24 hours reaches the threshold, the activation job sets the
daily_ai_credits_exceededoutput totrueand the agent job is skipped for that run. The conclusion job still runs and creates this report.The guardrail is evaluated at activation time, not retrospectively, so a single very large run that pushes usage over the threshold only blocks subsequent runs in the same window — it does not cancel a run that is already in progress.
How to disable this guardrail
Set
max-daily-ai-credits: -1in the workflow frontmatter to explicitly disable the guardrail, then recompile:Alternatively, remove the
max-daily-ai-creditskey entirely to fall back to the enterprise-wide default (if one is configured) or to run with no per-workflow cap.github-actions commentedon Oct 8, 2026
Agent job 37743054918 failed.
Warning
Daily Workflow AIC Guardrail Exceeded: The agent was not started because the 24-hour guardrail total reached the configured AI Credits threshold.
10.7KAI Credits735AI Credits10KAI Credits10KAI CreditsEstimated credits represent conservative per-run maximums where accounting is unavailable, not confirmed consumption. Subsequent scans retry unresolved accounting and replace estimates if recorded usage becomes available. Otherwise, these estimates stop counting when the affected runs leave the rolling 24-hour window.
Recorded AIC values are approximate; estimates are not measured consumption. Consult the billing dashboards for accurate usage and charges.
How to raise the daily limit
Set
max-daily-ai-creditsin your workflow frontmatter to a higher value, then recompile:Common suffix shorthands:
K= thousands,M= millions (e.g.2M= 2,000,000).After editing the workflow source file, regenerate the compiled lock file:
Commit and push the updated
.lock.ymlfile.What is the daily AI Credits guardrail?
The
max-daily-ai-creditsfrontmatter option sets a per-workflow spending cap measured in AI Credits across the 24-hour window before the current run. The cap is scoped to the repository and workflow — it aggregates usage across all runs of this workflow regardless of who triggered them.When the total of recorded AI Credits and unresolved conservative estimates across all completed runs of this workflow in the last 24 hours reaches the threshold, the activation job sets the
daily_ai_credits_exceededoutput totrueand the agent job is skipped for that run. The conclusion job still runs and creates this report.The guardrail is evaluated at activation time, not retrospectively, so a single very large run that pushes usage over the threshold only blocks subsequent runs in the same window — it does not cancel a run that is already in progress.
How to disable this guardrail
Set
max-daily-ai-credits: -1in the workflow frontmatter to explicitly disable the guardrail, then recompile:Alternatively, remove the
max-daily-ai-creditskey entirely to fall back to the enterprise-wide default (if one is configured) or to run with no per-workflow cap.github-actions commentedon Oct 8, 2026
Agent job 37745558478 failed.
Warning
Daily Workflow AIC Guardrail Exceeded: The agent was not started because the 24-hour guardrail total reached the configured AI Credits threshold.
10.7KAI Credits693AI Credits10KAI Credits10KAI CreditsEstimated credits represent conservative per-run maximums where accounting is unavailable, not confirmed consumption. Subsequent scans retry unresolved accounting and replace estimates if recorded usage becomes available. Otherwise, these estimates stop counting when the affected runs leave the rolling 24-hour window.
Recorded AIC values are approximate; estimates are not measured consumption. Consult the billing dashboards for accurate usage and charges.
How to raise the daily limit
Set
max-daily-ai-creditsin your workflow frontmatter to a higher value, then recompile:Common suffix shorthands:
K= thousands,M= millions (e.g.2M= 2,000,000).After editing the workflow source file, regenerate the compiled lock file:
Commit and push the updated
.lock.ymlfile.What is the daily AI Credits guardrail?
The
max-daily-ai-creditsfrontmatter option sets a per-workflow spending cap measured in AI Credits across the 24-hour window before the current run. The cap is scoped to the repository and workflow — it aggregates usage across all runs of this workflow regardless of who triggered them.When the total of recorded AI Credits and unresolved conservative estimates across all completed runs of this workflow in the last 24 hours reaches the threshold, the activation job sets the
daily_ai_credits_exceededoutput totrueand the agent job is skipped for that run. The conclusion job still runs and creates this report.The guardrail is evaluated at activation time, not retrospectively, so a single very large run that pushes usage over the threshold only blocks subsequent runs in the same window — it does not cancel a run that is already in progress.
How to disable this guardrail
Set
max-daily-ai-credits: -1in the workflow frontmatter to explicitly disable the guardrail, then recompile:Alternatively, remove the
max-daily-ai-creditskey entirely to fall back to the enterprise-wide default (if one is configured) or to run with no per-workflow cap.github-actions commentedon Oct 8, 2026
Agent job 37747649768 failed.
Warning
Daily Workflow AIC Guardrail Exceeded: The agent was not started because the 24-hour guardrail total reached the configured AI Credits threshold.
10.6KAI Credits648AI Credits10KAI Credits10KAI CreditsEstimated credits represent conservative per-run maximums where accounting is unavailable, not confirmed consumption. Subsequent scans retry unresolved accounting and replace estimates if recorded usage becomes available. Otherwise, these estimates stop counting when the affected runs leave the rolling 24-hour window.
Recorded AIC values are approximate; estimates are not measured consumption. Consult the billing dashboards for accurate usage and charges.
How to raise the daily limit
Set
max-daily-ai-creditsin your workflow frontmatter to a higher value, then recompile:Common suffix shorthands:
K= thousands,M= millions (e.g.2M= 2,000,000).After editing the workflow source file, regenerate the compiled lock file:
Commit and push the updated
.lock.ymlfile.What is the daily AI Credits guardrail?
The
max-daily-ai-creditsfrontmatter option sets a per-workflow spending cap measured in AI Credits across the 24-hour window before the current run. The cap is scoped to the repository and workflow — it aggregates usage across all runs of this workflow regardless of who triggered them.When the total of recorded AI Credits and unresolved conservative estimates across all completed runs of this workflow in the last 24 hours reaches the threshold, the activation job sets the
daily_ai_credits_exceededoutput totrueand the agent job is skipped for that run. The conclusion job still runs and creates this report.The guardrail is evaluated at activation time, not retrospectively, so a single very large run that pushes usage over the threshold only blocks subsequent runs in the same window — it does not cancel a run that is already in progress.
How to disable this guardrail
Set
max-daily-ai-credits: -1in the workflow frontmatter to explicitly disable the guardrail, then recompile:Alternatively, remove the
max-daily-ai-creditskey entirely to fall back to the enterprise-wide default (if one is configured) or to run with no per-workflow cap.github-actions commentedon Oct 8, 2026
Agent job 37752021539 failed.
Warning
Daily Workflow AIC Guardrail Exceeded: The agent was not started because the 24-hour guardrail total reached the configured AI Credits threshold.
10.6KAI Credits625AI Credits10KAI Credits10KAI CreditsEstimated credits represent conservative per-run maximums where accounting is unavailable, not confirmed consumption. Subsequent scans retry unresolved accounting and replace estimates if recorded usage becomes available. Otherwise, these estimates stop counting when the affected runs leave the rolling 24-hour window.
Recorded AIC values are approximate; estimates are not measured consumption. Consult the billing dashboards for accurate usage and charges.
How to raise the daily limit
Set
max-daily-ai-creditsin your workflow frontmatter to a higher value, then recompile:Common suffix shorthands:
K= thousands,M= millions (e.g.2M= 2,000,000).After editing the workflow source file, regenerate the compiled lock file:
Commit and push the updated
.lock.ymlfile.What is the daily AI Credits guardrail?
The
max-daily-ai-creditsfrontmatter option sets a per-workflow spending cap measured in AI Credits across the 24-hour window before the current run. The cap is scoped to the repository and workflow — it aggregates usage across all runs of this workflow regardless of who triggered them.When the total of recorded AI Credits and unresolved conservative estimates across all completed runs of this workflow in the last 24 hours reaches the threshold, the activation job sets the
daily_ai_credits_exceededoutput totrueand the agent job is skipped for that run. The conclusion job still runs and creates this report.The guardrail is evaluated at activation time, not retrospectively, so a single very large run that pushes usage over the threshold only blocks subsequent runs in the same window — it does not cancel a run that is already in progress.
How to disable this guardrail
Set
max-daily-ai-credits: -1in the workflow frontmatter to explicitly disable the guardrail, then recompile:Alternatively, remove the
max-daily-ai-creditskey entirely to fall back to the enterprise-wide default (if one is configured) or to run with no per-workflow cap.github-actions commentedon Oct 8, 2026
Agent job 37754348568 failed.
Warning
Daily Workflow AIC Guardrail Exceeded: The agent was not started because the 24-hour guardrail total reached the configured AI Credits threshold.
10.6KAI Credits585AI Credits10KAI Credits10KAI CreditsEstimated credits represent conservative per-run maximums where accounting is unavailable, not confirmed consumption. Subsequent scans retry unresolved accounting and replace estimates if recorded usage becomes available. Otherwise, these estimates stop counting when the affected runs leave the rolling 24-hour window.
Recorded AIC values are approximate; estimates are not measured consumption. Consult the billing dashboards for accurate usage and charges.
How to raise the daily limit
Set
max-daily-ai-creditsin your workflow frontmatter to a higher value, then recompile:Common suffix shorthands:
K= thousands,M= millions (e.g.2M= 2,000,000).After editing the workflow source file, regenerate the compiled lock file:
Commit and push the updated
.lock.ymlfile.What is the daily AI Credits guardrail?
The
max-daily-ai-creditsfrontmatter option sets a per-workflow spending cap measured in AI Credits across the 24-hour window before the current run. The cap is scoped to the repository and workflow — it aggregates usage across all runs of this workflow regardless of who triggered them.When the total of recorded AI Credits and unresolved conservative estimates across all completed runs of this workflow in the last 24 hours reaches the threshold, the activation job sets the
daily_ai_credits_exceededoutput totrueand the agent job is skipped for that run. The conclusion job still runs and creates this report.The guardrail is evaluated at activation time, not retrospectively, so a single very large run that pushes usage over the threshold only blocks subsequent runs in the same window — it does not cancel a run that is already in progress.
How to disable this guardrail
Set
max-daily-ai-credits: -1in the workflow frontmatter to explicitly disable the guardrail, then recompile:Alternatively, remove the
max-daily-ai-creditskey entirely to fall back to the enterprise-wide default (if one is configured) or to run with no per-workflow cap.github-actions commentedon Oct 8, 2026
Agent job 37758301251 failed.
Warning
Daily Workflow AIC Guardrail Exceeded: The agent was not started because the 24-hour guardrail total reached the configured AI Credits threshold.
10.5KAI Credits546AI Credits10KAI Credits10KAI CreditsEstimated credits represent conservative per-run maximums where accounting is unavailable, not confirmed consumption. Subsequent scans retry unresolved accounting and replace estimates if recorded usage becomes available. Otherwise, these estimates stop counting when the affected runs leave the rolling 24-hour window.
Recorded AIC values are approximate; estimates are not measured consumption. Consult the billing dashboards for accurate usage and charges.
How to raise the daily limit
Set
max-daily-ai-creditsin your workflow frontmatter to a higher value, then recompile:Common suffix shorthands:
K= thousands,M= millions (e.g.2M= 2,000,000).After editing the workflow source file, regenerate the compiled lock file:
Commit and push the updated
.lock.ymlfile.What is the daily AI Credits guardrail?
The
max-daily-ai-creditsfrontmatter option sets a per-workflow spending cap measured in AI Credits across the 24-hour window before the current run. The cap is scoped to the repository and workflow — it aggregates usage across all runs of this workflow regardless of who triggered them.When the total of recorded AI Credits and unresolved conservative estimates across all completed runs of this workflow in the last 24 hours reaches the threshold, the activation job sets the
daily_ai_credits_exceededoutput totrueand the agent job is skipped for that run. The conclusion job still runs and creates this report.The guardrail is evaluated at activation time, not retrospectively, so a single very large run that pushes usage over the threshold only blocks subsequent runs in the same window — it does not cancel a run that is already in progress.
How to disable this guardrail
Set
max-daily-ai-credits: -1in the workflow frontmatter to explicitly disable the guardrail, then recompile:Alternatively, remove the
max-daily-ai-creditskey entirely to fall back to the enterprise-wide default (if one is configured) or to run with no per-workflow cap.github-actions commentedon Oct 8, 2026
This issue was automatically closed because it expired on 2026-10-08T10:39:06.345Z.