From 5c3d58dd124bb968ff5cc863861dade41bf2039f Mon Sep 17 00:00:00 2001 From: Ly Nguyen Date: Mon, 9 Oct 2023 11:23:47 -0700 Subject: [PATCH] Fold in feedback --- .../release-notes/03-Oct-2023/native-retry-support-rn.md | 2 +- website/docs/docs/deploy/retry-jobs.md | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/website/docs/docs/dbt-versions/release-notes/03-Oct-2023/native-retry-support-rn.md b/website/docs/docs/dbt-versions/release-notes/03-Oct-2023/native-retry-support-rn.md index 0c90a6af212..25d2fbcef40 100644 --- a/website/docs/docs/dbt-versions/release-notes/03-Oct-2023/native-retry-support-rn.md +++ b/website/docs/docs/dbt-versions/release-notes/03-Oct-2023/native-retry-support-rn.md @@ -7,7 +7,7 @@ date: 2023-10-06 sidebar_position: 10 --- -Previously in dbt Cloud, you could rerun an errored job from start but now you can rerun it from the job run's point of failure. +Previously in dbt Cloud, you could only rerun an errored job from start but now you can also rerun it from its of failure. You can view which job failed to complete successully, which command failed in the run step, and choose how to rerun it. To learn more, refer to [Retry jobs](/docs/deploy/retry-jobs). diff --git a/website/docs/docs/deploy/retry-jobs.md b/website/docs/docs/deploy/retry-jobs.md index 12f60bb1d13..389f9d4640c 100644 --- a/website/docs/docs/deploy/retry-jobs.md +++ b/website/docs/docs/deploy/retry-jobs.md @@ -10,7 +10,7 @@ If your dbt job run completed with a status of `result:error` , you can rerun it - You have a [dbt Cloud account](https://www.getdbt.com/signup). - You must be using [dbt version](/docs/dbt-versions/upgrade-core-in-cloud) 1.6 or newer. -- There does not exist a more recent run of the job that completed successfully. The latest status of the run is `error`. +- The more 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). ## Rerun an errored job @@ -21,7 +21,7 @@ If your dbt job run completed with a status of `result:error` , you can rerun it 4. Examine the error message and determine how to fix it. After you have made your changes, save and commit them to your [Git repo](/docs/collaborate/git-version-control). 5. Return to your job’s **Run** page. In the upper right corner, click **Rerun** and choose **Rerun from start** or **Rerun from failure**. - If you choose to rerun from the failure point, a **Rerun failed steps** modal will appear. It lists the run steps it will invoke which will include the failed step and the steps it previously wasn’t able to invoke (skipped steps). To confirm, click **Rerun from failure**. The job reruns from the failed command in the previously failed run. This is denoted at the top of the **Run Summary** tab by a message "This run resumed execution from last failed step". + If you chose to rerun from the failure point, a **Rerun failed steps** modal opens. It lists the run steps it will invoke: the failed step and any skipped steps. To confirm these run steps, click **Rerun from failure**. The job reruns from the failed command in the previously failed run. A banner at the top of the **Run Summary** tab captures this with the message, "This run resumed execution from last failed step".