Your workspace is on the Hobby plan (trialing), and during high-traffic periods, builds for Free and Hobby tiers can be temporarily queued while Pro/Enterprise workloads are prioritized. Queued deployments process automatically once capacity frees up, and your most recent deployment did complete successfully. If you need uninterrupted deploys during these windows, upgrading to the Pro plan bypasses the queue entirely.

OK, thank you for fast response.

The last deploy was successful because I removed all others that didn't work (after chatting with the bot), so I thought it wasn't because of the plan as there is no sign that I'm getting "Limited Access" (the bot told me to check for it).

So I'll try again a deploy and leave on the queue, but regarding this limited capacity isn't there any information on the platform that can show us that we are being limited in capacity usage due to the plan type?

I'm asking because I guess it would help in converting new users to paying users as in my case, without a notification in the platform, I was believing the platform itself was malfunctioning and I didn't want to upgrade afraid of paying for something that seemed to not being working properly (appeared to be an internal problem and not just a plan issue).

Good news first: the queue backlog is cleared and your latest deployment built and went live at 19:35 UTC, so you should be able to deploy freely now.

To be transparent about what happened: this was a deploy queue backlog on our side today that mostly affected trial workspaces, and it has been fixed. It was not normal plan-based prioritization, so you did not do anything wrong and there was no "Limited Access" state to find.

And your feedback is a fair one. The in-product messaging during this incident was misleading (it blamed GitHub), and there is no clear indicator showing why a deployment is queued. We are passing that along internally. Thanks for spelling out the trust impact, that framing helps make the case.

Thank you for the transparent reply, it went back to working normally as you mentioned and I'm happy to hear that my feedback could be useful, just the fact that you guys monitored the message and gave this answer (even if I'm just a trial user) says a lot of good things about the company and helps to build trust to invest more on it, and that is really important to me because as I'm building something to serve other users I can only be as reliable to them as the platforms I'm using are to me.