13 Replies
fabienne
fabienne10mo ago
ZITADEL Docs
Search all matching executions. By default all executions of the instance are returned that have at least one execution target.
fabienne
fabienne10mo ago
ZITADEL Docs
List all available methods which can be used as condition for executions.
fabienne
fabienne10mo ago
these should be the right links sorry for the inconvenience, we will update the action docs with the right links and examples @Elio fyi
Unknown User
Unknown User10mo ago
Message Not Public
Sign In & Join Server To View
fabienne
fabienne10mo ago
we do have the actions v1 wich are implemented on some specific function in the login process action v2 is only available with requests at the moment with registered you mean a user create through the management console? yes as our ui also uses our apis, you can user the actions on the user create api request
Unknown User
Unknown User10mo ago
Message Not Public
Sign In & Join Server To View
fabienne
fabienne10mo ago
yes exactly at the moment we still have the v1 apis implemented in the console
vf-tyler
vf-tylerOP9mo ago
@fabienne Are any of the /resources/v3alpha endpoints available on the cloud-hosted version? I can't seem to find one that doesn't return:
{
"code": 5,
"message": "Not Found"
}
{
"code": 5,
"message": "Not Found"
}
I still am having trouble figuring out how to access Actions V2 as well. It seems like anytime documentation is referenced for Actions V2 it just points to the V3 endpoints.
fabienne
fabienne9mo ago
I think this relates to the following, we are already looking into it: https://github.com/zitadel/zitadel/issues/8507
GitHub
[Bug]: v3alpha example curl commands in docs always return not-foun...
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 current main Database Postgre...
vf-tyler
vf-tylerOP8mo ago
@fabienne Circling back to this, I can confirm the majority of the v3alpha endpoints are now functional, but it is still not possible to search executions using this endpoint: /resources/v3alpha/actions/executions/_search. It seems that the response is always:
{
"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"
}
]
}
{
"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"
}
]
}
fabienne
fabienne8mo ago
Hi @vf-tyler I quickly verified this, and can confirm that i get the same error, would you mind creating an issue for that?
vf-tyler
vf-tylerOP8mo ago
@fabienne No problem, an issue has been created: https://github.com/zitadel/zitadel/issues/8723
GitHub
[Bug]: /resources/v3alpha/actions/executions/_search always resul...
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 No response Database None D...
fabienne
fabienne8mo ago
thanks

Did you find this page helpful?