Never mind... I found the answer... it was basically stuck so I initiated a second delete action and it processed in short order.
Issue Deleting Custom Domain on Static Web App
I attempted to remove a domain I setup from the list of custom domains and the action is still apparently in progress nearly two hours later.
I've refreshed the view on the screen, refreshed the browser window and even logged out of Azure and back in and still the view sows the action is still chuggin along... is this standard fare response on this type of action or is there some way to force complete the action?
Thanks in advance for any help.
4 additional answers
Sort by: Most helpful
-
James Powell 1 Reputation point
2022-08-17T09:06:26.04+00:00 I too had this today. I initiated the delete, and it sat there 'deleting' but seemingly doing nothing. Refreshed, refreshed the portal and still stuck.
So I initiated a delete again on the 'deleting' record, and same.
Via the CLI....I get
Are you sure you want to perform this operation? (y/n): y
After deleting a custom domain, there can be a 15 minute delay for the change to propagate.
(Unspecified)
Code: Unspecified
Message:
az>> -
James Powell 1 Reputation point
2022-08-17T09:34:16.44+00:00 Ended up deleting the SWA. Some gremlins in there I think.
-
Martin Gertsen 1 Reputation point
2022-09-08T13:27:23.657+00:00 I experienced exactly the same as jpowell, and ended up having to delete the SWA as well.
There's an hour I won't get back sigh
-
Daren Chandisingh 1 Reputation point
2022-09-13T17:59:10.5+00:00 I found I had problems deleting custom domains on my SWAs after I tried to set them up with CloudFlare. I think it doesn't work properly with proxied CNAMES, so I tried to delete them to start again.
Even after a day they were still "deleting".
In the end I managed to delete them by selecting each one in turn, deleting it and then waiting patiently until the notification said it had been deleted. Not navigating away or trying to delete another one before the first had completed.
That worked reliably and I was able to delete all four problematic entries.