# List Scenario Runs — Dataiku

> Retrieve the last runs of a DSS scenario. Use this after Run Scenario, which returns no run identifier of its own, to follow the outcome: each entry carries a runId, start/end timestamps and a result object reporting outcome (e.g. SUCCESS)…

- Key: `dataiku-list-scenario-runs`
- Type: Action (Read-only)
- Version: 0.0.2
- App: Dataiku (`dataiku`) — https://pipedream.com/apps/dataiku.md
- This page (HTML): https://pipedream.com/apps/dataiku/actions/list-scenario-runs
- Hints: read-only · open-world
- Source: https://github.com/PipedreamHQ/pipedream/blob/master/components/dataiku/actions/list-scenario-runs/list-scenario-runs.mjs

## Description

Retrieve the last runs of a DSS scenario. Use this after **Run Scenario**, which returns no run identifier of its own, to follow the outcome: each entry carries a `runId`, `start`/`end` timestamps and a `result` object reporting `outcome` (e.g. `SUCCESS`) and `type` (e.g. `SCENARIO_DONE`). This tool cannot tell you which entry corresponds to a run you started: the response is just the scenario's recent runs, so a concurrent run, or one already in progress before you called **Run Scenario**, looks no different. Correlate deliberately — match on the `start` timestamp (the `runId`, e.g. `2016-04-15-16-57-37-759`, is derived from it) against the moment you triggered the run, rather than assuming any particular entry is yours. Stop polling once the run you are tracking reports a `result`, whatever its outcome. Requires the `RUN_JOBS` privilege on the project. [See the documentation](https://doc.dataiku.com/dss/api/15/rest/#scenarios-scenario-get-3)

## Props

| Prop | Type | Required | Description |
|---|---|---|---|
| `projectKey` | `string` | Yes | The key of the DSS project, e.g. MYPROJECT. Call List Projects and pass the projectKey field of the project you want. This is an identifier, not the project's display name — a display name will not resolve. In the Dataiku DSS GUI the same value appears in the project's URL as /projects/MYPROJECT/. |
| `scenarioId` | `string` | Yes | The ID of the scenario within the project, e.g. STEPS_SCENARIO. Call List Scenarios and pass the id field of the scenario you want — a scenario also has a separate name (its display label), which this prop does not accept. |
| `limit` | `integer` | No | Maximum number of past runs to retrieve, e.g. 20. Omit to let DSS apply its own default. |

## Run it

**MCP**

```ts
import { Client } from "@modelcontextprotocol/sdk/client/index.js"
import { StreamableHTTPClientTransport } from "@modelcontextprotocol/sdk/client/streamableHttp.js"
import { PipedreamClient } from "@pipedream/sdk"

const pd = new PipedreamClient({
  projectId: process.env.PIPEDREAM_PROJECT_ID!,
  clientId: process.env.PIPEDREAM_CLIENT_ID!,
  clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
  projectEnvironment: "production",
})

const accessToken = await pd.rawAccessToken

const transport = new StreamableHTTPClientTransport(
  new URL("https://remote.mcp.pipedream.net/v3"),
  {
    requestInit: {
      headers: {
        Authorization: `Bearer ${accessToken}`,
        "x-pd-project-id": process.env.PIPEDREAM_PROJECT_ID!,
        "x-pd-environment": "production",
        "x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
        "x-pd-app-slug": "dataiku",
      },
    },
  },
)

const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)

const { tools } = await mcp.listTools()

// listTools() hands your model this tool's input schema, so it can
// fill the arguments itself:
const result = await mcp.callTool({
  name: "dataiku-list-scenario-runs",
  arguments: {
    projectKey: "Project Key",
    scenarioId: "Scenario ID",
  },
})
```

**TypeScript**

```ts
import { PipedreamClient } from "@pipedream/sdk"

const pd = new PipedreamClient({
  projectId: process.env.PIPEDREAM_PROJECT_ID!,
  clientId: process.env.PIPEDREAM_CLIENT_ID!,
  clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
  projectEnvironment: "production",
})

const result = await pd.actions.run({
  id: "dataiku-list-scenario-runs",
  externalUserId: "{external_user_id}", // any stable ID for this user in your system
  configuredProps: {
    dataiku: { authProvisionId: "apn_xxxxxxx" },
    projectKey: "Project Key",
    scenarioId: "Scenario ID",
  },
})

console.log(result)
```

**cURL**

```bash
curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
  -H "Content-Type: application/json" \
  -H "X-PD-Environment: production" \
  -H "Authorization: Bearer {access_token}" \
  -d '{
    "external_user_id": "{external_user_id}",
    "id": "dataiku-list-scenario-runs",
    "configured_props": {
      "dataiku": { "authProvisionId": "apn_xxxxxxx" },
      "projectKey": "Project Key",
      "scenarioId": "Scenario ID"
    }
  }'
```

---

- App: https://pipedream.com/apps/dataiku.md · All apps: https://pipedream.com/apps