RHey there @Rimian! Thanks for reaching out - I'd love to troubleshoot this with you before looping in an engineer. Can you give me a bit more context on what you're building & what you're using with Zitadel? It would be helpful if you could structure your post similarly to what's outlined in questions-help-bugs(🏁 Start here - READ ME!) Forum post template & resources
SDoes it only happen when being redirected from your app or even if you try to access the console directly?
R@Rimian Hi there! Thank you for providing this context - Do you still experience this error when attempting to login with another admin or user account that doesn't have your email address?
RHey @Rimian - Let's try eliminating any possible session conflicts first. Could you clear your browser cookies & sessions for the Zitadel domain, then restart the browser and try logging in again? OR you could try using an incognito browser tab.
SHey @Rimian sorry for replying late. I do not work for Zitadel and only help out in my personal free time. In this case I checked in during my lunch break. Long story short, I won't always reply immediately. You can recognize the Zitadel time by color of their user names.
RWere you also using/testing actions on your account, by chance?
RHey @Rimian, so sorry for the delay! Based on this circumstance - You should check out and follow the guidelines outlined in https://zitadel.com/docs/legal/policies/account-lockout-policy
What you could also do is delete this current instance and then create a new instance without the conflicting emails. :gigipixel:
What you could also do is delete this current instance and then create a new instance without the conflicting emails. :gigipixel:
