Sorry you are having trouble!

I was able to recreate this. When you redeployed the most recent deployment, it used the snapshot from that deployment, which had 1 replica baked into its config. The replica count you'd set to 2 was stored separately, so the redeploy didn't pick it up, and the UI is now stuck showing "scaling" because it sees the mismatch but nothing is running to create the 2nd instance.

To fix this, try setting replicas back to 1, then back to 2. That should trigger a fresh scale operation and get both replicas running. If that doesn't work, a fresh deploy (rather than redeploying an old one) should also pick up the correct config.

Let me know if that gets you unstuck!