View as Markdown
Dataiku icon

Dataiku ACTION

List Scenario Runs

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
  • Action
  • Read only
  • API key
  • SDK
  • MCP

IMPLEMENTATION

Call this tool

Connect a user's Dataiku account once, then configure and run List Scenario Runs from your backend or agent.

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)

SCHEMA

Inputs

Pipedream supplies the connected account. Your application provides the operation-specific values below. Dynamic inputs are resolved against that user's account.

List Scenario Runs inputs
Property Type Description
projectKey Project Key string
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/.
Required
scenarioId Scenario ID string
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.
Required
limit Limit integer
Maximum number of past runs to retrieve, e.g. 20. Omit to let DSS apply its own default.
Optional

REFERENCE

Tool details

Behavior hints are published with the component in the Pipedream registry and surface as MCP tool annotations, so an agent can reason about a tool before it calls it.

Registry key
dataiku-list-scenario-runs
Version
0.0.2
App
Dataiku
Authentication
API key
Read-only
Yes
Destructive
No
Open world
Yes