Aident logoAident logo centerAident Loadout
Use CasesPricingDocs
ENStart Now
AppsDatabricks ToolsDatabricks List Runs
Databricks Tools

Databricks List Runs

Tool to list Databricks job runs in descending order by start time. Use when you need to retrieve job runs with optional filtering by job ID, run status, and type. Supports pagination via offset and limit parameters. Runs are automatically removed after 60 days.

Write actionRisk level 2 of 5API key connection
Use Databricks List Runs

Pricing and limits

Aident logo

Product

Aident LoadoutAident Playbook EditorOpen-CUAK

About

AppsSkillsUse CasesDocsBlogPricingDownloadsPrivacy PolicyTerms of Service

Alternatives

vs Composiovs Zapier
llms.txtGet an AI summary of Aident LoadoutSummarize with ChatGPTSummarize with ClaudeSummarize with GeminiSummarize with Perplexity

© Aident Labs, 2024-2026

Pricing
Free
Unified payment
Not currently supported

Inputs

  • limitinteger
    The number of runs to return. This value should be greater than 0 and less than 1000. The default value is 20. If 0 is specified, uses maximum limit.
  • job_idinteger
    The job for which to list runs. If omitted, the Jobs service will list runs from all jobs.
  • offsetinteger
    The offset of the first run to return, relative to the most recent run. Used for pagination.
  • run_typestring
    The type of runs to return. Supported values: JOB_RUN, WORKFLOW_RUN, SUBMIT_RUN.
  • active_onlyboolean
    If true, only active runs are included in the results (PENDING, RUNNING, TERMINATING states); otherwise, lists both active and completed runs. Cannot be true when completed_only is true.
  • expand_tasksboolean
    Whether to include task and cluster details in the response. When true, provides comprehensive information about each run's tasks and associated clusters.
  • start_time_tointeger
    Show runs that started at or before this value (epoch milliseconds). Use with start_time_from to filter runs by time range.
  • completed_onlyboolean
    If true, only completed runs are included in the results. Cannot be true when active_only is true.
  • start_time_frominteger
    Show runs that started at or after this value (epoch milliseconds). Use with start_time_to to filter runs by time range.

Observable output

  • data
    Required
    Data from the action execution
  • errorstring
    Error if any occurred during the execution of the action
  • successfulboolean
    Required
    Whether or not the action execution was successful or not

Skills that use this Action

Related use cases

No verified related use cases are linked yet.

Official source

Provider source

Skills that use this Action

No published Skills explicitly reference this Action yet.