GitHub Enterprise Cloud: Copilot AI credit usage reports created via REST API remain stuck in "processing"

[DavidTirea]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

API

Body

Summary

Copilot ai_credit usage reports created programmatically through the REST API remain indefinitely in the processing status. Equivalent reports requested manually from the GitHub web interface complete successfully and can be downloaded.

I opened GitHub Support ticket #4826809 on October 8, 2026, but it is still pending. I am posting here to determine whether anyone has encountered the same behavior or can confirm the expected API requirements.

Environment

• Product: GitHub Enterprise Cloud
• Data residency: European Union
• Authentication: GitHub App installation access token
• Report type: ai_credit
• Number of affected reports: 11
• First observed: October 1, 2026

Endpoint

Reports are created using:

POST /enterprises/{enterprise}/settings/billing/reports

Their status is subsequently checked using:

GET /enterprises/{enterprise}/settings/billing/reports

The request is sent to our GitHub Enterprise Cloud data-residency endpoint. The hostname and enterprise-specific details have been omitted for privacy.

Request

Headers:

Accept: application/vnd.github+json
Authorization: Bearer <installation_access_token>
X-GitHub-Api-Version: 2026-03-10
Content-Type: application/json

Example payload:

{
  "report_type": "ai_credit",
  "start_date": "2026-09-01",
  "end_date": "2026-09-30",
  "send_email": false
}

Actual behavior

The POST request is accepted and returns a report ID with the status processing. This indicates that authentication and authorization appear to succeed.

However:

• The status never transitions to completed or failed.
• The download_urls field remains empty.
• The reports have remained in this state for several days.
• This behavior is consistently reproducible for reports created through the REST API.
• We currently have 11 reports stuck in this state.

Example sanitized response:

{
  "id": "<redacted-report-id>",
  "report_type": "ai_credit",
  "status": "processing",
  "download_urls": []
}

Expected behavior

The report should eventually transition to either:

• completed, with one or more values in download_urls; or
• failed, with information indicating why it could not be generated.

Important comparison

Reports with the same ai_credit type and equivalent date ranges complete successfully when requested manually through the GitHub web interface using the Get usage report button.

The equivalent web-generated reports become completed, and their CSV files can be downloaded successfully.

The issue therefore appears to affect only reports created through the REST API.

Questions

1. Is ai_credit fully supported by the usage-report REST API for GitHub Enterprise Cloud?
2. Does this report type require an additional GitHub App permission, API parameter, or different authentication method?
3. Is X-GitHub-Api-Version: 2026-03-10 valid for this endpoint?
4. Has anyone experienced reports remaining indefinitely in processing?
5. Is there a known workaround other than generating the reports manually from the web interface?
6. Can GitHub Support or the engineering team manually cancel or clean up the reports that are already stuck?

We have stopped creating additional API reports while this is being investigated to avoid adding more reports to the processing queue.

Any guidance or confirmation would be appreciated.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐