Unable to execute "Deploy to Container App with Copilot" action multiple times

[v-ruizh]

OS: Win 11
Build Version: 0.11.0

Repro Steps:

1. Execute "Deploy to Container App with Copilot..." action for a container app (update the port by editing the summary view if your container image does not use port 80), succeed to execute the action the first time.
2. Right-click the same container app and run "Deploy to Container App with Copilot..." action again using the default summary.
3. Check the result of the second deployment attempt.

Expect:
The "Deploy to Container App with Copilot..." action should execute successfully on subsequent attempts.

Actual:
An error occurs when executing the action a second time.

[motm32]

Thank you for reporting this issue!

I think this seems like a timing issue and may not be related to the "Deploy to Container App with Copilot..." command specifically. Does something similar occur if you run the "Deploy to Container App..." command in quick subsequent deployments using the same inputs as was provided by copilot in "Deploy to Container App with Copilot..."?

[v-ruizh]

Yes, this issue also reproduces when running "Deploy to Container App..." command.

This bug is not consistently reproducible. After multiple attempts, it occurred twice on the third deployment and once on the fifth deployment.

[MicroFish91]

Sorry to ask this so late, I originally skipped over reviewing this because I thought it was a Copilot feature specific bug.

Could you repro this and provide some additional details:

1. Take a screenshot of the error message and provide it again (exactly how you did it above)
2. Wait 30s-1m
3. Refresh the tree view
4. Inspect the container app using View Properties
5. Provide values for the following: latestRevisionName, latestReadyRevisionName, latestRevisionFqdn, runningStatus, and scale (most interested in min/max replicas)

Thank you!

[v-ruizh]

Sorry to ask this so late, I originally skipped over reviewing this because I thought it was a Copilot feature specific bug.

Could you repro this and provide some additional details:

1. Take a screenshot of the error message and provide it again (exactly how you did it above)
2. Wait 30s-1m
3. Refresh the tree view
4. Inspect the container app using View Properties
5. Provide values for the following: latestRevisionName, latestReadyRevisionName, latestRevisionFqdn, runningStatus, and scale (most interested in min/max replicas)

Thank you!

1. This is the screenshot for the error message. (This error occurs when deploying the fourth time using the extension build 20260331.3.)
   
2. Please get the values for the following: latestRevisionName, latestReadyRevisionName, latestRevisionFqdn, runningStatus, and scale.
   
   This is the whole property file.
   property.txt

[MicroFish91]

We should investigate and get a solution in for this as part of the next release cycle. Likely ScaledToZero is an intermediate state that we're seeing before it finally resolves to Running. We have a built-in timeout limit during which we poll the final ready state, this explains why we only see this happen on occasion.

We have some options to investigate here:

• Should we simply extend the polling time?
• Should we consider ScaledToZero an okay result?
• Instead of errors, should these show up as warnings instead?