Error fetching billing plan
Something went wrong when submitting your build(s)
no account given: BillingPlanForAccount(). Status code: 500
Build failed
Why is that so?
11 Likes
We are having the exact same issue. We sent a ticket, it could be an issue on Unity’s side.
5 Likes
Same here.
3 Likes
Same for us. Is there some status page that we could watch? It is blocking our release pipeline.
No, it’s still not acknowledged in https://status.unity.com/ 
1 Like
We are having the same issue
I still can’t build it, so I can’t deploy it.
bump, same issue here
Unity is aware of the issue and investigating it, see https://status.unity.com for status updates
3 Likes
Hi folks,
Thank you for raising this issue, and for your patience with this. We are indeed aware of the issue and are currently investigating. I will update this thread when I have more information or the issue is resolved. The status page will also be updated.
Hi everyone,
This issue should now be resolved. Please reach out to the Service Support Team, or let me know here if that doesn’t seem to be the case.
Thanks for your patience while we got this corrected!
1 Like
Same issue, and of course their link to documentation points to nothing: https://support.unity.com/hc/en-us/articles/4413710653204…
2 Likes
Same issue, worked great in the morning but another build failed and this error appeared
1 Like
Same issue. Please resolve.
1 Like
Same issue here.
1 Like
Same issue. Please resolve.
Hi there,
We experienced a service interruption earlier today. The build automation team has been notified and is investigating the issue.
We will update this thread once we have more information.
I apologize for any inconvenience this may have caused.
2 Likes
are you aware of this?
1 Like
Yes, we are aware of the issue and have been working on resolving it.
We apologize for the inconvenience this has caused and the disruption to your day to day operations when using UBA. We understand that stability and reliability in a cloud service is extremely important and the impact that our quality has on your work.
This issue is now resolved. If you continue to encounter this issue please open a support ticket.