Why the previous is still in Undeploying status

Hi Ryan,

You should be able to replace the published model directly without waiting for the old one to be fully removed. Custom Translator supports publishing a different trained model to replace the existing one in the same region.

Since the previous model has been stuck in Undeploying since September 4, I would avoid repeatedly retrying the same operation. Check whether the new model can be selected under Publish model and published to the same region.

If the portal will not allow that because the old deployment is still locked in Undeploying, it likely needs to be cleared on the service side. There are recent Q&A cases where Custom Translator deployment states became stuck and normal portal actions could not remove them.

At that point, open an Azure Support request and include the project, model/category ID, region, when the undeployment started, and the operation details. Ask them to clear the stuck deployment state.

I would not delete the project or recreate the Translator resource while this operation is still stuck.