3b706954-03fd-4837-9638-970f34405604

Issue appears to have been resolved automatically.

@Stefan I realized after creating my issue that we might have the same issue. Mine is a cron that stopped running. To me, it's not working right now. Could you check if it's working for you rigght now?

https://discord.com/channels/713503345364697088/1259517941599174656

My app eventually built, though I had to redeploy a couple of times and abort the previous deployments. I hope your issue gets resolved soon!

Update for y'all @Stefan and @alvar, so we have deployed a possible fix tightening up the scheduling workflow when it comes to build resolution.

The good news is that as of late, we are stately running builds, the problem is that it's eventually consistent, the word eventually doing a lot of work here.

Our founder Cooper is on it as we speak.

Much thanks! I'm noticing this issue as well.

just now you have experienced this issue again?

Correct

I've done a few pushes today. Most of them have worked (though the build process was slow). Now it's suck on "Create container"

Doing a re-deploy seems to have worked for the moment though.

incident called -> <#846875565357006878>

team is still working on a fix for this, please check
for updates

this was marked as resolved, let us know if you experience this issue again!

please cancel and redeploy

Still not resolved

Stuck on creating containers

Same issue here

Same issue here. Also all my live hosted sites are broken

Not sure if others will find solutions here, but I'm trying to switch my region

Did you had success getting the services live?

I did get the services live, but I would 100% not do it. My MongoDB data did not replicate correctly

cc @Ray for viz

!s