Hey Yashwanth, we are deciding to update our migration doc to make it more robust, thanks to your question as these errors should be well defined and the setup should be easy enough to troubleshoot. while we're doing it, you can read up on this issue meanwhile that might help you understanding about the duplicate key value violates unique constraint duplicate key value violates unique constraint error. In short, its an error that triggers a retry mechanism when there is a collision of the sequence as part of the primary key. Maybe reading up the isue above clears up some doubts while we do a rework, but feel free to ask any followups if needed. Thanks
Hi @Yashwanth apologies that I missed the difference keyword. Both the error happens during user creation phase BUT at different stages , error 1 "duplicate key value violates unique constraint" happens at the database level when ZITADEL attempts to insert the user record while the error-2 occurs before any databse operation ZITADEL first queries the event store to check if a user with this ID exists, and rejects the creation request before attempting database operations. You can read about Zitadel's event store here https://zitadel.com/docs/concepts/eventstore/overview#what-is-an-event-store if that helps.