Repository navigation
[aw] SqlClient Issue Auto-Triage exceeded daily AI credits budget #4705
Description
Workflow Failure
Workflow: SqlClient Issue Auto-Triage
Branch: main
Run: https://github.com/dotnet/SqlClient/actions/runs/35205919124
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/dotnet/SqlClient/actions/runs/35205919124
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/dotnet/SqlClient/actions/runs/35205919124
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 issue-triage failure in https://github.com/dotnet/SqlClient/actions/runs/35205919124
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 SqlClient Issue Auto-Triage · ◷
Metadata
Metadata
Assignees
Type
Projects
- Status
Activity
github-actions commentedon Sep 17, 2026
Agent job 35205855391 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.github-actions commentedon Sep 17, 2026
Agent job 35205980452 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.github-actions commentedon Sep 17, 2026
Agent job 35206193943 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.
5.3KAI 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.github-actions commentedon Sep 17, 2026
Agent job 35206179393 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.
5.3KAI 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.github-actions commentedon Sep 17, 2026
Agent job 35206207829 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.
5.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.github-actions commentedon Sep 17, 2026
Agent job 35206267273 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.
5.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.github-actions commentedon Sep 17, 2026
Agent job 35206326194 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.
5.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.github-actions commentedon Sep 17, 2026
Agent job 35206405829 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.
5.6KAI 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.github-actions commentedon Sep 17, 2026
Agent job 35206466625 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.
5.7KAI 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.github-actions commentedon Sep 17, 2026
Agent job 35206392505 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.
5.7KAI 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.github-actions commentedon Sep 17, 2026
Agent job 35206527412 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.
5.7KAI 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.github-actions commentedon Sep 17, 2026
Agent job 35206647138 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.
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.4 remaining items
github-actions commentedon Sep 17, 2026
Agent job 35206995157 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.
6.1KAI 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.github-actions commentedon Sep 17, 2026
Agent job 35207056651 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.
6.2KAI 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.github-actions commentedon Sep 17, 2026
Agent job 35207322738 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.
6.4KAI 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.github-actions commentedon Sep 17, 2026
Agent job 35207257859 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.
6.4KAI 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.github-actions commentedon Sep 17, 2026
Agent job 35207403570 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.
6.6KAI 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.github-actions commentedon Sep 17, 2026
Agent job 35207387925 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.
6.6KAI 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.github-actions commentedon Sep 17, 2026
Agent job 35207465583 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.
6.6KAI 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.github-actions commentedon Sep 17, 2026
Agent job 35207529912 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.
6.7KAI 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.github-actions commentedon Sep 17, 2026
Agent job 35243505099 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.
11.3KAI 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.github-actions commentedon Sep 17, 2026
Agent job 35250089332 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.
11.3KAI 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.priyankatiwari08 commentedon Sep 22, 2026
This report was caused by the large backlog-triage batch on September 17 exhausting the workflow's rolling 24-hour AI-credit allowance. The configured threshold was 5,000 credits; later reports showed approximately 11,300 credits of recorded usage.
The spending guardrail was working as intended: it prevented subsequent runs from starting the AI agent. Usage can exceed the threshold because the check happens at activation using recorded usage and does not cancel agents already running.
No code repair, budget increase, or disabling of the guardrail is needed for this historical incident. It is separate from the placeholder-comment defect addressed by #4706. In the September 21 run 35655733263, the activation check recorded approximately 242 credits against the 5,000-credit threshold and allowed the agent to start, confirming that the earlier budget block was no longer preventing that run.
As older usage leaves the rolling window, new runs can start without changing the limit. However, previously skipped runs do not automatically complete their missing triage work; any still-needed summaries require a new, controlled retry after the submission fix is deployed.
For backlog recovery, retain the current limit and use small batches with budget checks, waiting for complete runs including bookkeeping before proceeding. Thus no action is required to raise/reset the budget or repair the guardrail; controlled recovery of skipped work remains a separate follow-up.
priyankatiwari08 commentedon Oct 5, 2026
Closing this historical budget-limit report as not planned / working as designed, rather than claiming a code fix was merged.
The September backlog-triage burst exhausted the rolling 24-hour AI-credit allowance. The guardrail correctly blocked subsequent agents; no budget increase or guardrail removal is needed.
Rechecked on October 5: the October 2 run on
main, https://github.com/dotnet/SqlClient/actions/runs/37002881060, recordedDaily workflow AIC guardrail not exceeded (0/5000), started the agent, and published a complete triage summary on #4778: #4778 (comment). This confirms the historical budget block is no longer preventing execution, with the 5,000-credit guardrail still enabled.This closure does not mark skipped backlog work as recovered. That recovery remains tracked in #4704, and the separate placeholder/submission defect and stronger output validation remain tracked by #4706 and #4716. Previously skipped work needs controlled retries where still relevant; it is not automatically replayed when the budget window clears.