How to clean up Zitadel after botched import
This issues pretty much explains what I tried to do: https://github.com/zitadel/zitadel/issues/10417
0. I exported data from old Zitadel.
1. I tried importing but because the preferred language contained
2. After replacing all
3. However, various constraint checks failed and so the imported org missed certain settings and thus the user's lacked the domain
4. I removed the imported organization and tried importing once again, but this time there were even more errors and the organization did not appear at all.
Now I am stuck in a situation where I can't see the imported organization in the GUI and no users, but neither can I import it because it exists somewhere internally. I get errors like these:
0. I exported data from old Zitadel.
1. I tried importing but because the preferred language contained
en-u-rg-uszzzz , the import failed2. After replacing all
en-u-rg-uszzzz with en, I tried importing again3. However, various constraint checks failed and so the imported org missed certain settings and thus the user's lacked the domain
4. I removed the imported organization and tried importing once again, but this time there were even more errors and the organization did not appear at all.
Now I am stuck in a situation where I can't see the imported organization in the GUI and no users, but neither can I import it because it exists somewhere internally. I get errors like these:
GitHub![[Bug]: Import saves data even when it fails · Issue #10417 · zita...](https://images-ext-1.discordapp.net/external/UqJovaanq3hKnev0IgSkogLxXXrNilYtMe50hw_rkmg/https/opengraph.githubassets.com/8ba1a123a3fa24324183c46052f3a47b2741eb939091fcc897753d1879373e21/zitadel/zitadel/issues/10417)
Preflight Checklist I could not find a solution in the documentation, the existing issues or discussions I have joined the ZITADEL chat Environment ZITADEL Cloud Version v3.3.2 Database PostgreSQL ...
