I encountered an error when setting user-level budget limits for my organization's Copilot business. How can I resolve this?

[GritworldSha]

🏷️ Discussion Type

Question

💬 Feature/Topic Area

Copilot in GitHub

Body

When I tried to set user-level budget limits for members within my organization, I encountered the error shown in the image. It indicated that I had already set a budget limit, but I couldn't find the corresponding user-level budget limit in my budget limit table.

[GritworldSha]

We are using Copilot Business. I set user-level budget limits at the organization level. Regarding permissions, I am the owner of the organization, and I encounter the same issue when setting up using an alternate owner account.

[ICWG-DavidYang]

I’m experiencing the same issue with Copilot Business user-level budget settings.

In my case, I’m an organization admin/owner, and I can access:

Organization Settings → Billing and licensing → Budgets and alerts

I already created or attempted to create a user-level budget for a specific user. The first time, it seemed to be created successfully. However, it does not appear anywhere in the Budgets and alerts list. The page only shows organization-level budgets, such as:

• All AI Credit SKUs
• Codespaces
• Packages
• Actions
• Git LFS

When I try to create the same user-level budget again, GitHub shows this error:

“A budget for this product and scope already exists. Please edit the existing budget instead of creating another.”

The problem is that there is no visible user-level budget entry in the UI, so I cannot edit or delete the existing one.

Current environment:

• Product: GitHub Copilot Business
• Billing scope: Organization level
• Budget type: Users / user-level budget
• Organization-level All AI Credit SKUs budget is visible and editable
• User-level budget appears to exist in the backend, but is not shown in the Budgets and alerts list
• AI usage page only shows organization-level usage and an Edit budget link, but I still cannot find the existing user-level budget

This looks like a hidden or orphaned user-scoped budget record, or a UI issue where user-level Copilot AI credit budgets are not being displayed under organization Budgets and alerts.

Could GitHub please clarify where existing user-level Copilot AI credit budgets should appear in the UI, or provide a way to locate/edit/delete hidden user-level budget records?

This is blocking us because the user hit the monthly limit, but we cannot find the existing user-level budget to increase it.

[webfeilang]

I’m experiencing the same issue.

Today is the first day our organization switched to the Copilot Business AI Credits model. When I opened VS Code this morning, everyone in the organization was unable to use Copilot and was prompted to set an organizational budget limit.

To test the feature, I set a $1 user-level budget for two users. However, in the Budgets and alerts page, I cannot see any of the user-level budgets I created.

At the moment, most users in the organization can use Copilot normally again, but the two test users are still blocked because they have already exceeded the $1 budget limit. Since the budgets are not visible in the UI, I’m unable to edit or remove them.

Is there any workaround or way to resolve this? This is quite urgent for us.

[od-ekhosbayar]

same issue

[r-ueno-ask]

Thank you very much.
In our organization, we accidentally set a $0 budget for all users, which prevented anyone from using Copilot. However, after retrieving the budget ID via the GitHub API, we were able to reset the budget by deleting it. This was very helpful.

• Check
  • gh api /organizations/ORG_NAME/settings/billing/budgets
• Delete:
  • gh api --method DELETE /organizations/ORG_NAME/settings/billing/budgets/BUDGET_ID

[shuu-uuhs]

Thanks guys!

It works, though the budget is still shown under the individual's GUI; the limitation was removed.

[EraYaN]

The UI should display the info in the webbrowser as well: https://github.com/organizations/{org}/settings/billing/multi_user_budget/{id} and allow editing.

[shaju007]

Here is a discussion on the same issue https://github.com/orgs/community/discussions/197549

[movedoa]

Same issue here

[fedem96]

Same issue

[paulox]

Same here

[Spacefish]

I can´t even see it via the API as it is on the second page and the first page only has 1 Organization level budget.
We have the setup with one Enterprise and multiple Organizations below that Enterprise. I am admin of one of the Organizations.
If i call the API directly it tells me that there are 11 total budgets, but i only get one.. Probably the 11th is my user budget, but i cant fetch it.

F:\> gh api /enterprises/OUR_ENTERPRISE/settings/billing/budgets?page=1
{
  "budgets": [
    {
      "id": "*****************",
      "budget_type": "BundlePricing",
      "budget_product_sku": "ai_credits",
      "budget_scope": "organization",
      "budget_amount": 5000,
      "prevent_further_usage": true,
      "budget_entity_name": "********",
      "budget_alerting": {
        "will_alert": true,
        "alert_recipients": [
          "****",
          "****",
          "****"
        ]
      }
    }
  ],
  "has_next_page": true,
  "total_count": 11
}

see the "has_next_page": true and "total_count": 11

But the second page is empty:

F:\> gh api /enterprises/OUR_ENTERPRISE/settings/billing/budgets?page=2
{
  "budgets": [],
  "has_next_page": false,
  "total_count": 11
}

I don´t know how hard you have to vibecode to get a different total count from the actually returned result, but then still manage to skip the element on page 2.. I mean i get it, you either pull all data from the DB and then permission filter the entries in the Backend (that´s probably whats happening here, as otherwise we wont get a larger total_count). But then you have to somehow paginate the filtered list instead of the unfiltered one? Wtf.. github devs..

Hi everyone,

We have provided details in this discussion. Please subscribe to that post to receive real-time updates and a notification when the issue is resolved.

If you have further questions or additional details about your experience, please comment directly on the discussion linked above.

We appreciate your patience as we work toward a solution.