Repository navigation
[aw] PR Sous Chef exceeded daily AI credits budget #65356
Description
Activity
Agent job 37144310963 failed.
Warning
Daily Workflow AIC Guardrail Exceeded: The agent was not started because this workflow has already consumed the configured 24-hour AI Credits budget.
- 24h AIC usage:
5.6KAI Credits - Configured threshold:
5KAI Credits
The agent will resume automatically once the 24-hour rolling window resets. No action is required if the current limit is appropriate for your usage.
AIC values are approximate. 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:max-daily-ai-credits: 20K
Common 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 compile
Commit and push the updated
.lock.ymlfile.[!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-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 aggregated AI Credits usage across all completed runs of this workflow in the last 24 hours exceeds 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
[!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: -1in the workflow frontmatter to explicitly disable the guardrail, then recompile:max-daily-ai-credits: -1
gh aw compile
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.Generated from PR Sous Chef · ◷
- 24h AIC usage:
Agent job 37148205834 failed.
Warning
Daily Workflow AIC Guardrail Exceeded: The agent was not started because this workflow has already consumed the configured 24-hour AI Credits budget.
- 24h AIC usage:
5.5KAI Credits - Configured threshold:
5KAI Credits
The agent will resume automatically once the 24-hour rolling window resets. No action is required if the current limit is appropriate for your usage.
AIC values are approximate. 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:max-daily-ai-credits: 20K
Common 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 compile
Commit and push the updated
.lock.ymlfile.[!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-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 aggregated AI Credits usage across all completed runs of this workflow in the last 24 hours exceeds 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
[!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: -1in the workflow frontmatter to explicitly disable the guardrail, then recompile:max-daily-ai-credits: -1
gh aw compile
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.Generated from PR Sous Chef · ◷
- 24h AIC usage:
Agent job 37151702435 failed.
Warning
Daily Workflow AIC Guardrail Exceeded: The agent was not started because this workflow has already consumed the configured 24-hour AI Credits budget.
- 24h AIC usage:
5.5KAI Credits - Configured threshold:
5KAI Credits
The agent will resume automatically once the 24-hour rolling window resets. No action is required if the current limit is appropriate for your usage.
AIC values are approximate. 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:max-daily-ai-credits: 20K
Common 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 compile
Commit and push the updated
.lock.ymlfile.[!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-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 aggregated AI Credits usage across all completed runs of this workflow in the last 24 hours exceeds 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
[!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: -1in the workflow frontmatter to explicitly disable the guardrail, then recompile:max-daily-ai-credits: -1
gh aw compile
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.Generated from PR Sous Chef · ◷
- 24h AIC usage:
Agent job 37155977384 failed.
Warning
Daily Workflow AIC Guardrail Exceeded: The agent was not started because this workflow has already consumed the configured 24-hour AI Credits budget.
- 24h AIC usage:
5.3KAI Credits - Configured threshold:
5KAI Credits
The agent will resume automatically once the 24-hour rolling window resets. No action is required if the current limit is appropriate for your usage.
AIC values are approximate. 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:max-daily-ai-credits: 20K
Common 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 compile
Commit and push the updated
.lock.ymlfile.[!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-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 aggregated AI Credits usage across all completed runs of this workflow in the last 24 hours exceeds 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
[!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: -1in the workflow frontmatter to explicitly disable the guardrail, then recompile:max-daily-ai-credits: -1
gh aw compile
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.Generated from PR Sous Chef · ◷
- 24h AIC usage:
Agent job 37159647157 failed.
Warning
Daily Workflow AIC Guardrail Exceeded: The agent was not started because this workflow has already consumed the configured 24-hour AI Credits budget.
- 24h AIC usage:
5.2KAI Credits - Configured threshold:
5KAI Credits
The agent will resume automatically once the 24-hour rolling window resets. No action is required if the current limit is appropriate for your usage.
AIC values are approximate. 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:max-daily-ai-credits: 20K
Common 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 compile
Commit and push the updated
.lock.ymlfile.[!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-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 aggregated AI Credits usage across all completed runs of this workflow in the last 24 hours exceeds 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
[!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: -1in the workflow frontmatter to explicitly disable the guardrail, then recompile:max-daily-ai-credits: -1
gh aw compile
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.Generated from PR Sous Chef · ◷
- 24h AIC usage:
Agent job 37162758149 failed.
Warning
Daily Workflow AIC Guardrail Exceeded: The agent was not started because this workflow has already consumed the configured 24-hour AI Credits budget.
- 24h AIC usage:
5.1KAI Credits - Configured threshold:
5KAI Credits
The agent will resume automatically once the 24-hour rolling window resets. No action is required if the current limit is appropriate for your usage.
AIC values are approximate. 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:max-daily-ai-credits: 20K
Common 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 compile
Commit and push the updated
.lock.ymlfile.[!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-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 aggregated AI Credits usage across all completed runs of this workflow in the last 24 hours exceeds 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
[!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: -1in the workflow frontmatter to explicitly disable the guardrail, then recompile:max-daily-ai-credits: -1
gh aw compile
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.Generated from PR Sous Chef · ◷
- 24h AIC usage:
Agent job 37165697488 failed.
Warning
Daily Workflow AIC Guardrail Exceeded: The agent was not started because this workflow has already consumed the configured 24-hour AI Credits budget.
- 24h AIC usage:
5.1KAI Credits - Configured threshold:
5KAI Credits
The agent will resume automatically once the 24-hour rolling window resets. No action is required if the current limit is appropriate for your usage.
AIC values are approximate. 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:max-daily-ai-credits: 20K
Common 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 compile
Commit and push the updated
.lock.ymlfile.[!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-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 aggregated AI Credits usage across all completed runs of this workflow in the last 24 hours exceeds 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
[!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: -1in the workflow frontmatter to explicitly disable the guardrail, then recompile:max-daily-ai-credits: -1
gh aw compile
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.Generated from PR Sous Chef · ◷
- 24h AIC usage:
Agent job 37169638753 failed.
Warning
Daily Workflow AIC Guardrail Exceeded: The agent was not started because this workflow has already consumed the configured 24-hour AI Credits budget.
- 24h AIC usage:
5KAI Credits - Configured threshold:
5KAI Credits
The agent will resume automatically once the 24-hour rolling window resets. No action is required if the current limit is appropriate for your usage.
AIC values are approximate. 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:max-daily-ai-credits: 20K
Common 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 compile
Commit and push the updated
.lock.ymlfile.[!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-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 aggregated AI Credits usage across all completed runs of this workflow in the last 24 hours exceeds 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
[!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: -1in the workflow frontmatter to explicitly disable the guardrail, then recompile:max-daily-ai-credits: -1
gh aw compile
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.Generated from PR Sous Chef · ◷
- 24h AIC usage:
This issue was automatically closed because it expired on 2026-10-04T05:33:47.494Z.
Closed by Workflow
Workflow Failure
Workflow: PR Sous Chef
Branch: main
Run: https://github.com/github/gh-aw/actions/runs/37140851111
Warning
Daily Workflow AIC Guardrail Exceeded: The agent was not started because this workflow has already consumed the configured 24-hour AI Credits budget.
5.8KAI Credits5KAI CreditsThe agent will resume automatically once the 24-hour rolling window resets. No action is required if the current limit is appropriate for your usage.
AIC values are approximate. 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 aggregated AI Credits usage across all completed runs of this workflow in the last 24 hours exceeds 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.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:
Debug with any coding agent
Use this prompt with any coding agent (GitHub Copilot, Claude, Gemini, etc.):
Manually invoke the agent
Debug this workflow failure using your favorite Agent CLI and the
agentic-workflowsprompt.agentic-workflowsskill from.github/skills/agentic-workflows/SKILL.mdor https://github.com/github/gh-aw/blob/main/.github/skills/agentic-workflows/SKILL.mddebug the agentic workflow pr-sous-chef failure in https://github.com/github/gh-aw/actions/runs/37140851111Tip
Stop reporting this workflow as a failure
To stop a workflow from creating failure issues, set
report-failure-as-issue: falsein its frontmatter: