From 21abafadc2891af02abefd795c73c57bdba3a7de Mon Sep 17 00:00:00 2001
From: Doug Beatty <44704949+dbeatty10@users.noreply.github.com>
Date: Thu, 12 Dec 2024 17:43:56 -0700
Subject: [PATCH] `dbt retry` will only work if dbt can parse the project and
 generate a manifest

---
 website/docs/docs/deploy/retry-jobs.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/website/docs/docs/deploy/retry-jobs.md b/website/docs/docs/deploy/retry-jobs.md
index f439351aec5..4e3ad0d429f 100644
--- a/website/docs/docs/deploy/retry-jobs.md
+++ b/website/docs/docs/deploy/retry-jobs.md
@@ -10,6 +10,7 @@ If your dbt job run completed with a status of **Error**, you can rerun it from
 
 - You have a [dbt Cloud account](https://www.getdbt.com/signup).
 - You must be using [dbt version](/docs/dbt-versions/upgrade-dbt-version-in-cloud) 1.6 or newer.
+- dbt can successfully parse the project and generate a [manifest](/reference/artifacts/manifest-json)
 - The most recent run of the job hasn't completed successfully. The latest status of the run is **Error**.
     - The job command that failed in the run must be one that supports the [retry command](/reference/commands/retry).