cuddly-jelly-27016
08/19/2025, 12:09 AMgrpcui to query ListExecutions
grpcurl -plaintext -H "<user A token>" -d '{
"id": {
"project": "66ac1f956fd5b26a885904ce",
"domain": "development"
},
"limit": 5,
"sortBy": {
"key": "created_at"
}
}' localhost:9089 flyteidl.service.AdminService.ListExecutions
Then select the execution from the response, and view the execution identity at response.executions[0].spec.security_context.run_as.execution_identity
### Relaunch
The above all applies to the RelaunchExecution grpc endpoint as well, however this endpoint does not appear to be exposed via the UI so it is a less immediate concern.
#### Relaunch via gRPC
You can use a tool like grpcurl to query RelaunchExecution
grpcurl -plaintext -H "<user A token>" -d '{
"id": {
"project": "66ac1f956fd5b26a885904ce",
"domain": "development",
"name": "easily-ruling-crappie-aeps"
}
}' localhost:9089 flyteidl.service.AdminService.RelaunchExecution
(note that this endpoint is not exposed via e.g. the Flyte UI)
### Screenshots
No response
### Are you sure this issue hasn't been raised already?
• Yes
### Have you read the Code of Conduct?
• Yes
flyteorg/flytecuddly-jelly-27016
08/19/2025, 12:09 AM