From 48aedfe450947cd4baad7bba0902bea6e049b485 Mon Sep 17 00:00:00 2001
From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com>
Date: Fri, 22 May 2026 01:25:12 +0000
Subject: [PATCH 1/2] docs: document retriggering failed workflow runs
---
workflows/manage.mdx | 17 +++++++++++++++--
1 file changed, 15 insertions(+), 2 deletions(-)
diff --git a/workflows/manage.mdx b/workflows/manage.mdx
index 0064a7580..ec25ca9a9 100644
--- a/workflows/manage.mdx
+++ b/workflows/manage.mdx
@@ -1,7 +1,7 @@
---
title: "Manage workflows"
-description: "Trigger, disable, re-enable, and delete Mintlify workflows from your dashboard, and learn how schedules recalculate after you pause and resume a workflow."
-keywords: ["manage workflows", "trigger workflow", "disable workflow", "enable workflow"]
+description: "Trigger, disable, re-enable, retrigger, and delete Mintlify workflows from your dashboard, and learn how schedules recalculate after pauses."
+keywords: ["manage workflows", "trigger workflow", "disable workflow", "enable workflow", "retrigger workflow"]
---
## Disable a workflow
@@ -30,3 +30,16 @@ Each workflow keeps a log of past runs, including the status and a summary of ch
+
+## Retrigger a failed run
+
+If a workflow run fails, you can retrigger it to run again with the same configuration. Use this when a run fails because of a transient issue, like a temporary network error, and you want to retry without waiting for the next scheduled run or making another push.
+
+Retriggering is available for runs started by a schedule, a push event, or a manual trigger. Runs started by external integrations cannot be retriggered.
+
+1. Go to the [Workflows](https://dashboard.mintlify.com/products/workflows) page in your dashboard.
+2. Click a workflow to open its run history.
+3. Find a run with a **Failed** status.
+4. Click **Retrigger** on the run row, or open the run and click **Retrigger** in the detail panel.
+
+A new run starts with the same prompt, repositories, and trigger context as the original. The retriggered run appears as a new entry in the run history.
From 38bc3321fc5314391b31dd9a43883e24cce3cd4b Mon Sep 17 00:00:00 2001
From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com>
Date: Fri, 22 May 2026 01:27:19 +0000
Subject: [PATCH 2/2] docs: tighten retrigger run section wording
---
workflows/manage.mdx | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/workflows/manage.mdx b/workflows/manage.mdx
index ec25ca9a9..5421f3c3c 100644
--- a/workflows/manage.mdx
+++ b/workflows/manage.mdx
@@ -33,7 +33,7 @@ Each workflow keeps a log of past runs, including the status and a summary of ch
## Retrigger a failed run
-If a workflow run fails, you can retrigger it to run again with the same configuration. Use this when a run fails because of a transient issue, like a temporary network error, and you want to retry without waiting for the next scheduled run or making another push.
+If a workflow run fails, you can retrigger it to run again with the same configuration. This is useful when a run fails because of a transient issue, like a temporary network error, and you want to retry without waiting for the next scheduled run.
Retriggering is available for runs started by a schedule, a push event, or a manual trigger. Runs started by external integrations cannot be retriggered.