Project Grant Deactivation Access Restriction
Actions v2 on v3.1.0 returning [internal] An internal error occurred (QUERY-y2u7vctrha)
[internal] An internal error occurred (QUERY-y2u7vctrha)
and im not able to see my action that was added. Its not being triggered either-debug vs non -debug Zitadel images on ghcr
Error when connection to Zitadel console

Event compaction / snapshotting
sessions8
taking a bulk of that time. This is mostly garbage data because session TTL is set to 12h anyway and we have no use for "historical" information about sessions or auth requests.
By pruning or compacting the eventstore mirror
can be completed in a reasonable amount of time, which should help with downtime and the like....How to Allow Same Google User in Multiple ZITADEL Organizations?
Notifier errors since upgraded to 3.0.4
Is there a GO SDK Replacement for Rest /oath/v2/token
/oath/v2/token
? I looked through the documentation but it doesn't seem to be the case. I feel like I'm missing something though.How to create action to redirect when clicking reset password.
user.human.password.code.added
?
Organization with only external provider login redirecting to type in password

Store Password
is it possible to make auto-renewal of refresh token lifetime?
Locked out of instance
Flaky error from /oauth/v2/token
/oauth/v2/token
endpoint is returning a flaky error.
...Self Hosted Azure Container Apps - "Database "zitadel" already exists"
start-init
command, I get logs stating that the Zitadel database already exists. I also get logs stating that certain aspects of Zitadels config exist too (roles for example) before the container ultimately hangs. As I am just proving out elements of deployment, I'm deploying both to the same container app environment, both are freshly deployed each time, and i'm using env vars instead of config files. There are no volumes being mounted for the db container, as well as no sidecars or init containers. Initial thinking was maybe two zitadel containers where triggering the same init process on my single postgres instance, but after forcing just a single replica with a single container across both I still see the same issue. I have attached the terraform i'm using (obfuscating anything relating to my azure subscription) for reference, as well as the logs messages i'm seeing for both the postgres container and zitadel container. Fully anticipate I'm doing something daft, so any help is greatly appreciated!
(I'm also able to run the stack locally using compose, its just when I deploy to Azure its giving me errors.)...
Domain discovery with identity provider flow
GetUserGrantByID for granted projects not working
Can i move Users from OrgA to OrgB.
Creating local user in Zitadel V3