INDEX

get_run_logs maps to get-events, not to get-logs — despite its name it returns structured run events rather than compute logs.

The MCP server also offers run actions with no CLI counterpart. All three require deployment_name.

• rerun_run — re-execute a run. Params: run_id (required), strategy, use_parent_run_tags (default true), extra_tags.
• rerun_backfill — re-execute a backfill. Params: backfill_id (required), then the same as rerun_run.
• terminate_run — terminate an in-flight run. Params: run_id (required).

strategy is FROM_FAILURE (default), ALL_STEPS, or FROM_ASSET_FAILURE. Retrying only the failed portion of a run or backfill is the FROM_FAILURE default; pass ALL_STEPS to re-execute everything.

Reference Files Index

• dg api run get-events — debugging a run by reading its logs; filtering run events by level or step
• dg api run get-logs — fetching stdout stderr compute logs for a run; downloading step output logs
• dg api run get — details about a specific run
• dg api run launch — materializing assets or launching jobs on a Dagster Plus deployment; remote asset materialization, remote job launch
• dg api run list — listing or filtering runs