Skip to main content

​
When to use

  • Check the status of recent workflow runs at a glance
  • Find failed executions to investigate further
  • Monitor how often a workflow is triggered
  • Get an execution ID to pass to get-execution for node-level debugging

​
Prerequisites

  • codika CLI installed and authenticated
  • A deployed process instance (devProcessInstanceId or prodProcessInstanceId in project.json)
  • API key with executions:read scope

​
Command

codika list executions <processInstanceId> [options]

​
Arguments

ArgumentDescription
<processInstanceId>Process instance ID (dev or prod) from project.json

​
Options

OptionDescriptionDefault
--workflow-id <id>Filter results to a specific workflowAll workflows
--failed-onlyReturn only failed executionsOff
--limit <n>Number of executions to return (1–100)20
--api-url <url>Override API URL—
--api-key <key>Override API key—
--profile <name>Use a specific profile instead of the active one—
--jsonJSON output—

​
Behavior

  1. Fetches recent executions from the platform API
  2. Returns lightweight summaries (no full result data — use get execution for that)
  3. Sorted by creation time, newest first

​
Dev vs Prod executions

After deploying and publishing, project.json contains both instance IDs: 
{
  "devProcessInstanceId": "pi-dev-789",
  "prodProcessInstanceId": "pi-prod-999"
}
Use devProcessInstanceId to list dev executions and prodProcessInstanceId to list prod executions.

​
Examples

# List recent executions for dev instance
codika list executions pi_dev_456

# Filter by workflow
codika list executions pi_dev_456 --workflow-id main-workflow

# Only failed executions
codika list executions pi_dev_456 --failed-only

# Limit results
codika list executions pi_dev_456 --limit 5

# JSON output
codika list executions pi_dev_456 --json

# Prod executions (use prod instance ID from project.json)
codika list executions pi_prod_789

​
Output

● Recent Executions (pi_dev_456...)

  ID             Workflow             Status     Duration   Created
  ────────────── ──────────────────── ────────── ────────── ───────────────────
  exec-001abc    main-workflow        ✓ success  1.2s       2026-03-04 14:30:00
  exec-002def    main-workflow        ✗ failed   0.8s       2026-03-04 14:00:00
    └─ [HTTP Request] Connection refused
  exec-003ghi    helper-workflow      ⋯ pending  -          2026-03-04 13:30:00

  Showing 3 executions
Each row shows the execution ID (truncated), workflow ID, status with icon, duration, and creation timestamp. Failed executions show the error message and failed node name on the next line. Pass any execution ID to codika get execution <id> for full node-level details. Note: Zero executions is not an error — the CLI prints “No executions found.” and exits with code 0.

​
Error reference

HTTPErrorFix
401Invalid API keyRe-login with codika login
403Missing scopeCreate key with executions:read scope
403No accessProcess instance in different org
404Instance not foundCheck process instance ID

​
Exit codes

CodeMeaning
0Success
1API error
2CLI validation error