Max subscription was not activated.

[mcyenikoylu]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Copilot in GitHub

Body

I switched to Copilot Max in May. But I'm still listed as Pro+. The payment was charged to my credit card days ago, but I can't use my subscription.

Also, since June 1st, I've been paying a high token cost for very simple text corrections. Because the tasks I perform are standard, I can see an abnormally high token burn after the June transition. Copilot has become like a truck that burns 5 gallons of fuel per kilometer. It's very illogical.

I created a support ticket, but I think they'll respond next year. So what happens to the Max subscription fee I already paid?

[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. ⭐

[maheerCodes]

hey @mcyenikoylu 👋

ive seen this happen before,,, the billing goes through on the apple/payment side but githubs backend doesnt always flip the plan status immediately. its a sync issue between the payment processor and githubs subscription system, pretty frustrating when you have already been charged.

few things to check/try.

• go to github.com/settings/billing and check what plan it actually shows there,, sometimes the portal shows "Pro+" even when Max is active on the backend, or vice versa
• try signing out completely and back in,,, sounds silly but it forces a session refresh which sometimes picks up the correct plan status
• if you subscribed through the iOS app/apple subscriptions, the billing goes through apple not github directly. in that case github support needs to manually verify the receipt on their end.
• check that the email on your github account matches the one apple charged. mismatches here can cause the activation to silently fail.

about the high token usage since june.. yeah that does sound off for simple text corrections. once your plan gets sorted it might be worth checking if any extensions or IDE plugins are making extra background requests you're not aware of. that can burn tokens fast without you realising.

since you already raised a support ticket thats the right move, just make sure you include: the charge date, the amount, and a screenshot of the billing page showing Pro+ instead of Max. that'll help them locate the transaction faster.

hope they get back to you soon❤️❤️❤️, being charged for a plan you cant use is not okay...