thefufanu
thefufanu•4w ago

Actions V2 - An internal error occurred

We have a fresh setup with version 3.3.2, with minimal config parameters. When we call actions V2 in the console UI, this error message always appears, and created actions are accepted but not displayed in the UI. Has anyone encountered this message before and has any idea what we could do?
No description
3 Replies
Rajat
Rajat•4w ago
hey @thefufanu thanks for your question, what action did you try to trigger?. can you pls describe more of your issue?. Thanks
bawsky
bawsky•4w ago
Hello! I am also facing this issue (running v3.3.0) It was the first action I tried to setup on our instance (running in k8s). 
POST "/v2beta/actions/executions/_search"
response status: 500
response body:
{"code":13, "message":"An internal error occurred (QUERY-y2u7vctrha)", "details":[{"@type":"type.googleapis.com/zitadel.v1.ErrorDetail", "id":"QUERY-y2u7vctrha", "message":"An internal error occurred"}]}
POST "/v2beta/actions/executions/_search"
response status: 500
response body:
{"code":13, "message":"An internal error occurred (QUERY-y2u7vctrha)", "details":[{"@type":"type.googleapis.com/zitadel.v1.ErrorDetail", "id":"QUERY-y2u7vctrha", "message":"An internal error occurred"}]}
(note: it doesn't matter if I send a request body or not, the result is the same) (I unfortunately did not find a way to reproduce this error locally (with docker-compose)) On my case: I was trying to setup an action execution for the first time. Might also be relevant: I accidentally did a typo on the execution's event_type (oidc.session_added instead of oidc_session.added), I believe that might be the related of the crash.. not sure though as I couldn't really reproduce this locally (Zitadel won't let me create an execution with a non-existing event_type... perhaps I was able due to some race condition?). Since then I've deleted the action target, and now having a look at Zitadel's database I couldn't really find anything related to the action execution with a typo. Btw it'd be really helpful if there was some kind crash report/stacktrace to look at... The logs generated by Zitadel don't include anything helpful to debug this.
bawsky
bawsky•4w ago
Opened an issue to properly track this: https://github.com/zitadel/zitadel/issues/10492 hope to track the root cause and get this fixed 🤞 I saw a couple other people having similar issues with Actions V2 (here in discord)
GitHub
[Bug]: Actions V2 - Getting "An internal error occurred" when searc...
Preflight Checklist I could not find a solution in the documentation, the existing issues or discussions I have joined the ZITADEL chat Environment Self-hosted Version v3.3.0 Database PostgreSQL Da...

Did you find this page helpful?