# Common scheduling configurations

Get started with some examples of common schedules:

* [Build datasets regularly](#build-datasets-regularly)
* [Build datasets when new data is available](#build-datasets-when-new-data-is-available)
* [Advanced (multiple) trigger configurations](#advanced-multiple-trigger-configurations)
* [Update a dataset at a specific time *only* if its parent has been updated](#update-a-dataset-at-a-specific-time-only-if-its-parent-has-been-updated)

## Build datasets regularly

For this example, we want **raw\_taxi (cleaned)** to update every weekday at 9 AM, and we want to build not just **raw\_taxi (cleaned)** but also all of its upstream dependencies. We should configure our schedule as follows:

![image-time-based-full-page]

## Build datasets when new data is available

For this example, we want the schedule to run whenever another dataset has been updated. We can use the same configuration as in the previous section, with one small modification. An [event trigger](../triggers-reference/index.md#event-trigger) should be chosen, selecting which dataset(s) on the graph you wish to trigger the update.

![when-datasets-update]

For more details on event-based schedules, see the [event triggers](../triggers-reference/index.md#event-trigger) documentation.

## Advanced (multiple) trigger configurations

![image-of-any-trigger-config]
![image-of-or-trigger-config]

For this example, we want **Dataset D** to update at 9 AM daily, but also whenever the dataset it depends on, **Parent A**, sees a change. According to [the table of combinations for compound triggers](../triggers-reference/index.md#compound-trigger), if we combine a time-based trigger with an event-based trigger through an OR, the dataset will build at time T, as well as when event E occurs. Therefore, we will set the dataset we want to schedule the build for to **Dataset D**, and add a time-based trigger for 9 AM with an event-based trigger that watches for any update on **Parent A**. Choosing "Any of these triggers", or an advanced configuration and adding an OR between the conditions, are equivalent in this case.

## Update a dataset at a specific time *only* if its parent has been updated

![image-of-all-trigger-config]
![image-of-and-trigger-config]

For this example, we want **Dataset D** to update at 9 AM daily, but only if the dataset it depends on, **Parent A**, has seen a change. According to [the table of combinations for compound triggers](../triggers-reference/index.md#compound-trigger), if we combine a time-based trigger with an event-based trigger through an AND, the dataset will build at time T *if* event E has previously occurred. Therefore, we will set the dataset we want to schedule the build for to **Dataset D**, and add a time-based trigger for 9 AM with an event-based trigger that watches for any update on **Parent A**. Choosing "All of these triggers" or an advanced configuration and adding an AND between the conditions, are equivalent in this case.

:::callout{theme="warning"}
This configuration does not limit the time window in which **Parent A** has been updated. Whether it was updated at 8:55 AM on the same day or at 9:10 AM the day before, the event-based trigger will evaluate to TRUE at 9 AM, causing all criteria to be met and the schedule to run. This means that if **Parent A** is consistently updating *after* 9 AM, e.g. at 9:10 AM every day, then **Dataset D** will be built daily at 9 AM, with data from **Parent A** that is 23 hours and 50 minutes old.
:::

[image-time-based-full-page]: ../../../assets/a955cd3ac7951a968203bcfafd3a6b2663fd125f18cb431f66e2078acbb55b22.webp

[when-datasets-update]: ../../../assets/4780569d885a413bdb85be123897a711226d16592c6a410dccab097902708504.webp

[image-of-all-trigger-config]: ../../../assets/ddf587a9ef688c44ec2a1f268656b5455923fc4b9ef46a033ecc65bc3dd4a0a8.webp

[image-of-and-trigger-config]: ../../../assets/fa2e7b1a89086fae898721e6e901e511fad9cb298169819464e853c00d8971a2.webp

[image-of-or-trigger-config]: ../../../assets/3e46fdfb83c4e7c2d72cd56085a81dafc94815c9ecd3c45cc637bc988a917cae.webp

[image-of-any-trigger-config]: ../../../assets/1fd6c124c6f6b8c680583b5a83b7bf06d8bbbe54effe436e97fa22dadaaa005c.webp