List recent executions
list_recent_executionsList recent platform executions (deployments, write operations) for the current cluster, or across the whole organisation when the conversation is not opened on a cluster (pass cluster_id or cluster_name to narrow). Returns: id, name, status, error_excerpt, step_summary (succeeded/failed counts), and timestamps. Use this to investigate what changed recently or which deployments failed. Filter by status (e.g., 'failed', 'critical', 'running') for focused queries.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"cluster_id": "<cluster_id>"
},
"name": "list_recent_executions"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of executions to return. Default 10, max 50. | |
| status | No | Optional list of execution statuses to filter by. Use ['failed', 'critical'] to find recent failures. | |
| cluster_id | Yes | Ankra cluster id (UUID) the call targets. Discover ids with list_clusters. | |
| include_internal_executions | No | If true, also list the platform's internal maintenance executions that the default listing hides: GitOps reconcile ticks (name gitops_reconcile_attempt, 'GitOps reconcile') that landed no commit. A reconcile that pushed a 'Sync cluster state from Ankra' commit, possibly re-encrypting sealed files, is listed by default and names the commit and files in its detail's git_push. Default false; the same flag as the REST executions list's include_internal_executions. |