Retrying block runs from a pipeline run

​

Automatic retry

​

1. Global retry config

retry_config:
  # Number of retry times
  retries: 3
  # Initial delay (in seconds) before retry. If exponential_backoff is true,
  # the delay time is multiplied by 2 for the next retry
  delay: 5
  # Maximum accumulated retry delay before scheduling the next attempt
  max_delay: 60
  # Whether to use exponential backoff retry
  exponential_backoff: true

​

2. Block level retry config

blocks:
- uuid: example_data_loader
  type: data_loader
  upstream_blocks: []
  downstream_blocks: []
  retry_config:
    retries: 2
    delay: 5
    max_delay: 10
    exponential_backoff: false
  ...

​

3. Pipeline level retry_config

blocks:
- ...
- ...
- ...
retry_config:
  retries: 2
  delay: 5
  max_delay: 10
  exponential_backoff: false
  ...

​

Retry incomplete blocks

• Supported pipeline types: Standard, Streaming, and Integration pipelines
• If a pipeline run fails, you can retry from the failed block run instead of restarting the entire pipeline run. In Mage Pro, open the failed run’s actions menu from the pipeline’s Runs table and select Retry incomplete blocks. The separate Retry pipeline run action restarts the entire pipeline run. For Streaming pipelines, Retry incomplete blocks reuses the existing pipeline run, resets its incomplete block runs, and resumes it instead of creating a new run.
• You can also retry incomplete blocks from the individual pipeline run page (/pipelines/[pipeline_uuid]/runs/[pipeline_run_id]).
• At the top of the individual pipeline runs page, there should be a red Retry incomplete blocks button. Click on it, and the block runs should retry from the failed block.
• For Integration pipelines, this broad retry keeps the existing behavior and retries every incomplete stream in the run.

​

Retry a specific integration stream

• Supported pipeline types: Integration pipelines
• If a data integration pipeline run has a failed stream, go to the individual pipeline run page (/pipelines/[pipeline_uuid]/runs/[pipeline_run_id]).
• Select any block run row for the stream you want to retry. The selected row can be completed if another block run for that stream failed.
• At the top of the page, click the Retry button with the stream name shown next to it. Mage retries only the stream shown on the button and leaves other streams unchanged.

​

Retry from selected block

• Supported pipeline types: Standard and Integration pipelines
• If you want to retry block runs for a pipeline run starting from a specific block (regardless of the block run’s status), go to the same page for the individual pipeline run.
• Select a block run row, and a blue Retry from selected block button should appear.
• Note that the Retry from selected block button will only appear if the pipeline run is not currently running.
• For Integration pipelines, selecting a block run in a completed pipeline run keeps the existing selected-block retry behavior. Selecting a stream in an incomplete run uses the specific stream retry described above.
• If there is a failed block run and you try to retry from a selected block that is downstream from that failed block, you may get upstream_failed block run errors.

​

Accessing the individual pipeline runs page

1. Click on a pipeline from the main Pipelines Dashboard.
2. Click on the Runs section or on an individual trigger from the Triggers section.
3. Underneath the Block runs column of the pipeline runs table, there is a link that says something like See block runs (x). Click on that link to redirect to the individual pipeline runs page, which lists the blocks runs specific to a pipeline run.