This should be resolved now?

Still stuck. Build completes successfully and the image is pushed, but the deployment then sits in QUEUED indefinitely — it never gets a deployment slot. Specific example: deployment ID 91027984-2b3f-4532-bbf8-9d699632c464 (service pars-restaurant, Southeast Asia region) — build finished at 09:10:58 UTC, still QUEUED with no slot. Every deployment since the region change behaves this way. Please check deployment slot / scheduler allocation for this service. My POS is down for staff and we're blocked.

We looked into this. Your builds are completing and the image publishes fine, the problem is on our side after the move to Singapore: your service is being placed in the region and then immediately taken down, so nothing stays running. This isn't a configuration issue on your end, your setup is correct. We've handed this to the team that owns the Singapore region and will update you here as soon as it's back up. Apologies for the downtime on your POS.

Following up: the original service that was wedged in Singapore has been removed, and we can see a new pars-restaurant service that is now deploying successfully and running. It looks like things are back up on your end. If your POS is working again, we'll consider this resolved. Let us know if you hit any further trouble and we'll jump back in.