From bc01c9c477eb7d1ffb3155070f018e6264533263 Mon Sep 17 00:00:00 2001 From: Ly Nguyen <107218380+nghi-ly@users.noreply.github.com> Date: Wed, 21 Feb 2024 15:27:57 -0800 Subject: [PATCH] Update website/docs/docs/deploy/deploy-jobs.md Co-authored-by: Leona B. Campbell <3880403+runleonarun@users.noreply.github.com> --- website/docs/docs/deploy/deploy-jobs.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/docs/deploy/deploy-jobs.md b/website/docs/docs/deploy/deploy-jobs.md index ebdb7b1e327..a0c04b9a6b8 100644 --- a/website/docs/docs/deploy/deploy-jobs.md +++ b/website/docs/docs/deploy/deploy-jobs.md @@ -37,7 +37,7 @@ You can create a deploy job and configure it to run on [scheduled days and times - **Run source freshness** — Enable this option to invoke the `dbt source freshness` command before running the deploy job. Refer to [Source freshness](/docs/deploy/source-freshness) for more details. 4. Options in the **Triggers** section: - **Run on schedule** — Run the deploy job on a set schedule. - - **Timing** — Specify whether to [schedule](#schedule-days) the deploy job using **Intervals** that runs the job every specified number of hours, **Specific hours** that runs the job at specific times of day, or **Cron schedule** that runs the job specified using [cron syntax](#cron-schedule). + - **Timing** — Specify whether to [schedule](#schedule-days) the deploy job using **Intervals** that run the job every specified number of hours, **Specific hours** that run the job at specific times of day, or **Cron schedule** that run the job specified using [cron syntax](#cron-schedule). - **Days of the week** — By default, it’s set to every day when **Intervals** or **Specific hours** is chosen for **Timing**. - **Run when another job finishes** — Run the deploy job when another _upstream_ deploy [job completes](#trigger-on-job-completion). - **Project** — Specify the parent project that has that upstream deploy job.