Manage Subscription - Oops! Something went wrong | Community
Skip to main content

Manage Subscription - Oops! Something went wrong

  • October 13, 2023
  • 5 replies
  • 0 views

There seems to be an issue with the billing area, preventing me from changing the number of subscriptions on my account. This is the second time in the last couple of months I've attempted to update the number of seats we have, and both times, the page takes ~30 seconds to load, and then shows a message saying "Oops! Something went wrong". The first time, I did eventually manage to update my subscriptions, but it seems to be completely dependent on the below network request taking less than 30 seconds.

There is a network error shown in the browser console: POST https://billing.zendesk.com/billing/api/v1/subscription_previews?issuer=central_admin 503 (Service Unavailable).

How is it best to resolve this issue?

 

Full repo steps:

  1. Navigate to Admin
  2. Select Account -> Billing -> Subscriptions
  3. (wait for the page to load)
  4. Click Manage
  5. (wait for the page to load)
  6. Increase the number of Agents in Support
  7. (wait for the loading icons - ~30 seconds)
  8. Bug: Error message shown


The network request also shows the following response:
upstream connect error or disconnect/reset before headers. reset reason: connection termination


Please can this be looked into ASAP as this is preventing me assigning new employees licences.

5 replies

  • Author
  • October 17, 2023

Still happening this morning




Brett13
  • Community Manager
  • October 17, 2023
Hey Mark, 

Thanks for bringing this to our attention! I'm going to create a ticket on your behalf so our Customer Care team can follow up with you as soon as possible. You should receive an email shortly stating your ticket has been created.
 
Cheers! 

  • Author
  • October 17, 2023

Thanks Brett


  • Author
  • November 2, 2023

For anyone interested in following this - the issue still hasn't been resolved despite being passed through three different people. In addition, the support team seems to have created another issue and rather than getting a timeout, I'm now getting a 500 Internal Server error...


Brett13
  • Community Manager
  • November 3, 2023
Hey Mark, apologies for the delay in our response as we investigage this issue. I checked in on the ticket you referenced and it looks like our engineering team was able to get resolution for you. If this error happens again please let me know and thanks again for reporting this to us!