Troubleshooting a Failed Workflow Run

A workflow may fail to run if there’s a problem in how it was configured, for example, a missing field mapping, an incorrect condition, or an invalid step reference.

This guide walks you through how to troubleshoot configuration-related errors, correct the workflow setup, and re-run and resolve the failed instance using Workflow Runs.

Step 1: Fix the Workflow Configuration

If you found an issue in the workflow's setup, such as an incorrect configuration, you need to fix it before retrying the failed run.

  1. From the Workflow Run Details page, click Edit Workflow to open the workflow editor.

  2. In the Workflow Editor, make the necessary changes to correct the issue and click Save.

Step 2: Update the Failed Run with the Latest Workflow Blueprint

Once you’ve saved your changes, you need to apply the updated workflow blueprint to the specific failed run.

  1. Return to the Workflow Run Details page.

  2. Click Update from Blueprint to refresh the failed run with the latest version of the workflow. This replaces the previous, incorrect configuration with your updated one.

To make sure you have the latest version of your workflow, you can check the Last updated timestamp (e.g., "Last updated: Oct 17, 2025, 3:41:52 PM"), which is visible at the top of the page.

Step 3: Rerun the Workflow

Now that the workflow is fixed and the failed run is updated, you can try running it again.

  1. Click the Rerun button.

  2. The system will execute the workflow again, starting from the step that previously failed, not from the beginning.

    • If the rerun is successful, a new instance will not be added to the failed runs list.

    • If the rerun fails again, a new failed run will appear in the list with a new Run ID.

Step 4: Mark the Run as Resolved

Marking a run as resolved helps your team track which failures have been reviewed and addressed. After verifying the workflow has run successfully, click Mark as Resolved on the original failed run to update its status.

Marking a run as Resolved is for tracking purposes and will not change its original FAILED status.

You can also use this action without re-running the workflow. For instance, if the failure was caused by an external server issue that you have since fixed, you can simply mark the run as resolved.

Related Articles

Now that you know how to fix a workflow configuration issue from a failed workflow run, you can explore these related guides.