I am writing to request the release of a specific subdomain that is currently marked as “already taken” despite the original account being deleted.
I previously used a personal GitHub account to deploy an app. Recently, I started a new company and decided to migrate all my projects to a new organization account. To ensure a clean migration, I deleted the app and then completely deleted my previous personal Streamlit account.
Now, I have signed up with my new organization account and am trying to deploy the same app using the original subdomain. However, I am getting an “already taken” error message. Since the previous account and app no longer exist, this subdomain should be available.
Could you please help me release this subdomain so I can register it under my new organization account?
Hey there, thanks for reaching out and welcome to the Streamlit community! This is a common scenario when migrating apps and accounts. Even after deleting an app and the associated Streamlit account, sometimes the subdomain remains reserved due to backend records or caching, preventing immediate reuse. The subdomain should become available right after deletion, but in rare cases, manual intervention from the Streamlit support team is required to release it for reuse by a new account or organization.
To resolve this, you’ll need to submit a support case to Streamlit (Snowflake) with details about the subdomain and your new account. You can do this by following the steps in the official documentation: How to submit a support case for Streamlit Community Cloud. The support team will review your request and can manually release the subdomain for you.