Account stuck in "Awaiting Benefits" loop after approval.

[NobodyB4D]

🏷️ Discussion Type

Question

💬 Feature/Topic Area

Verification Help & Guidance

Hi everyone,

Hi everyone and GitHub Education Team,

My academic status was approved on August 11, 2026, but my account has been completely stuck on "Awaiting Benefits" for 28 days.

The system states that benefits become available after 72 hours, but neither GitHub Copilot nor the Student Developer Pack offers have unlocked yet. It seems the automated provisioning script failed to link the licenses to my profile.

Could a moderator or staff member please help refresh or manually re-trigger the provisioning process for my account?

Thank you for your time and help!

[Kushan20070126]

If your academic status was approved on August 11 but the account is still showing “Awaiting Benefits” after 28 days, this looks different from a normal verification delay.

I would check these first:

• Make sure you are signed into the same GitHub account used for the Education application.
• Open the GitHub Education benefits page and check whether the approval is still active.
• Check your email for any follow-up message from GitHub Education.
• Sign out and back in, then check the benefits page again.
• If it still shows “Awaiting Benefits”, contact GitHub Support and include the approval date, your GitHub username, and a screenshot of the current status.

I would not submit another Education application. The existing application is already approved.

Also, I would not expect a repository moderator to manually attach Copilot or Student Developer Pack benefits. This looks like an account-level provisioning issue, so GitHub Support is the better escalation path.

Since the status has remained unchanged for 28 days despite the stated 72-hour period, I would explicitly mention that when opening the support request.

[Humerous]

If your Education application already shows as approved, I would treat the verification step and the benefits-provisioning step as two separate stages.

At that point, repeatedly reapplying is unlikely to help if the account is already approved but remains stuck on "Awaiting Benefits."

I would check:

1. that the approved Education account is the same GitHub account currently signed in
2. that the verified school email is still attached to that account
3. whether the Education benefits page shows an approval date or only a pending/provisioning state
4. whether any Copilot or Student Developer Pack entitlement has partially appeared already

If approval happened weeks ago and the account is still stuck only at the provisioning stage, that sounds more like an account-side entitlement sync problem than a document-verification problem.

I would keep the existing approval evidence and contact GitHub Education Support with:

• the GitHub username
• approval date
• screenshot of the "Awaiting Benefits" state
• verified academic email
• any previous application/reference details

I would avoid submitting a new application unless Support specifically asks for one, because that could create another verification cycle instead of fixing the already-approved account.