Repository navigation
[aw] Dependabot PR Triage (skills-driven) exceeded daily AI credits budget #14739
Description
Workflow Failure
Workflow: Dependabot PR Triage (skills-driven)
Branch: trunk
Run: https://github.com/cli/cli/actions/runs/39141727797
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-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 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_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/cli/cli/actions/runs/39141727797
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/cli/cli/actions/runs/39141727797
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 dependabot-triage failure in https://github.com/cli/cli/actions/runs/39141727797
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 Dependabot PR Triage (skills-driven) · ◷
- expires on Oct 25, 2026, 3:43 PM UTC
Activity
cli-triage commentedon Oct 18, 2026
This is an auto-generated failure report (not a user bug report): the
dependabot-triageagentic workflow was skipped because it hit its configuredmax-daily-ai-creditsguardrail (5K AI Credits in the rolling 24h window). The same root cause — recurring daily AI-credit exhaustion for this workflow — has produced several prior near-identical issues, including #14728, #14715, and #14702 (still open). I'm suggestingduplicateof #14728 as the most recent prior occurrence; a maintainer should decide whether to consolidate these and instead raisemax-daily-ai-credits(or disable the guardrail) independabot-triage's workflow frontmatter if the current 5K cap is too low for actual usage, then recompile withgh aw compile. No command label applies since this isn't about a specificghcommand's behavior.cli-triage commentedon Oct 18, 2026
Agent job 39146364845 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.
5KAI 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.cli-triage commentedon Oct 18, 2026
Agent job 39150838854 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.
5KAI 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.cli-triage commentedon Oct 18, 2026
Agent job 39155587249 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.
5KAI 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.cli-triage commentedon Oct 18, 2026
Agent job 39160033715 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.
5KAI 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.cli-triage commentedon Oct 18, 2026
Agent job 39164611470 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.
5KAI 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.cli-triage commentedon Oct 18, 2026
Agent job 39169054016 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.
5KAI 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.cli-triage commentedon Oct 18, 2026
Agent job 39173414390 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.
5KAI 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.cli-triage commentedon Oct 18, 2026
Agent job 39177655122 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.
5KAI 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.cli-triage commentedon Oct 19, 2026
Agent job 39184390418 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.
5KAI 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.cli-triage commentedon Oct 19, 2026
Agent job 39187654143 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.
5KAI 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.cli-triage commentedon Oct 19, 2026
Agent job 39192025267 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.
5KAI 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.cli-triage commentedon Oct 19, 2026
Agent job 39196680353 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.
5KAI 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.cli-triage commentedon Oct 19, 2026
Agent job 39201591943 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.
5KAI 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.cli-triage commentedon Oct 19, 2026
Agent job 39206432225 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.
5KAI 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.timerloggedout-spec commentedon Oct 19, 2026
Use Responses to Fix your usage.
cli-triage commentedon Oct 19, 2026
Agent job 39214288457 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.
5KAI 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.cli-triage commentedon Oct 19, 2026
Agent job 39219343290 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.
5KAI 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.cli-triage commentedon Oct 19, 2026
Agent job 39226156348 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.
5KAI 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.cli-triage commentedon Oct 19, 2026
Agent job 39233359238 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.
5KAI 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.