Retry jobs

website/docs/docs/collaborate/git-version-control.md

@@ -22,3 +22,4 @@ When you develop in the command line interface (CLI) or Cloud  integrated develo
 - [Merge conflicts](/docs/collaborate/git/merge-conflicts) 
 - [Connect to GitHub](/docs/cloud/git/connect-github)
 - [Connect to GitLab](/docs/cloud/git/connect-gitlab)
+- [Connect to Azure DevOps](/docs/cloud/git/connect-azure-devops)

website/docs/docs/dbt-versions/release-notes/03-Oct-2023/native-retry-support-rn.md

@@ -0,0 +1,15 @@
+---
+title: "Enhancement: Native support for the dbt retry command"
+description: "October 2023: Rerun errored jobs from start or from the failure point"
+sidebar_label: "Enhancement: Support for dbt retry"
+tags: [Oct-2023, Scheduler]
+date: 2023-10-06
+sidebar_position: 10
+---
+
+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).
+
+
+<Lightbox src="/img/docs/deploy/native-retry.gif" width="70%" title="Example of the Rerun options in dbt Cloud"/>

website/docs/docs/deploy/retry-jobs.md

@@ -0,0 +1,32 @@
+---
+title: "Retry your dbt jobs" 
+sidebar_label: "Retry jobs"
+description: "Rerun your errored jobs from start or the failure point."
+---
+
+If your dbt job run completed with a status of `result:error` , you can rerun it from start or from the point of failure in dbt Cloud.
+
+## Prerequisites
+
+- 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.
+- 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
+
+1. Select **Deploy** from the top navigation bar and choose **Run History.** 
+2. Choose the job run that has errored. 
+3. In the **Run Summary** tab on the job’s **Run** page, expand the run step that failed. An :x: denotes the failed step. 
+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 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".
+
+<Lightbox src="/img/docs/deploy/native-retry.gif" width="70%" title="Example of the Rerun options in dbt Cloud"/>
+
+## Related content
+
+- [Run visibility](/docs/deploy/run-visibility)
+- [Jobs](/docs/deploy/jobs)
+- [Job commands](/docs/deploy/job-commands)

website/sidebars.js

@@ -352,6 +352,7 @@ const sidebarSettings = {
           link: { type: "doc", id: "docs/deploy/monitor-jobs" },
           items: [
             "docs/deploy/run-visibility",
+            "docs/deploy/retry-jobs",
             "docs/deploy/job-notifications",
             "docs/deploy/webhooks",
             "docs/deploy/artifacts",