Skip to content

Commit

Permalink
fix broken links
Browse files Browse the repository at this point in the history
  • Loading branch information
PedramNavid committed Aug 14, 2024
1 parent 28360a0 commit c7425c7
Showing 1 changed file with 8 additions and 8 deletions.
16 changes: 8 additions & 8 deletions docs/docs-next/docs/guides/automation.md
Original file line number Diff line number Diff line change
Expand Up @@ -23,8 +23,8 @@ helping you choose the right method for your needs. You will find links to more

Before continuing, you should be familiar with:

- [Asset definitions](concepts/assets)
- [Jobs](concepts/jobs)
- [Asset definitions](/concepts/assets)
- [Jobs](/concepts/ops-jobs)

</details>

Expand All @@ -42,7 +42,7 @@ Let's look at each method in more detail.
## Schedules

Schedules allow you to run jobs at specified times, like "every Monday at 9 AM" or "daily at midnight."
A schedule combines a selection of assets, known as a [Job](/concepts/jobs), and a [cron expression](https://en.wikipedia.org/wiki/Cron)
A schedule combines a selection of assets, known as a [Job](/concepts/ops-jobs), and a [cron expression](https://en.wikipedia.org/wiki/Cron)
in order to define when the job should be run.

To make creating cron expressions easier, you can use an online tool like [Crontab Guru](https://crontab.guru/).
Expand All @@ -64,8 +64,8 @@ For more information about how Schedules work, see the [About Schedules](/concep

Sensors allow you to trigger runs based on events or conditions, like a new file arriving or an external system status change.

Like schedules, sensors operate on a selection of assets, known as [Jobs](/concepts/jobs) and can either start a pipeline
through a [Run](/concepts/runs) or log a reason for not starting a pipeline using a [SkipReason](/concepts/sensors#skip-reasons).
Like schedules, sensors operate on a selection of assets, known as [Jobs](/concepts/ops-jobs) and can either start a pipeline
through a Run or log a reason for not starting a pipeline using a SkipReason.

However, unlike schedules, sensors are triggered by events that you define.
You must provide a function that the sensor will use to determine if it should trigger a run.
Expand Down Expand Up @@ -125,8 +125,8 @@ Use this table to help guide your decision:

## Next Steps

- Learn more about [advanced scheduling patterns](link-to-advanced-scheduling)
- Explore [complex sensor examples](link-to-sensor-examples)
- Dive into [Declarative Automation best practices](link-to-declarative-automation)
- Learn more about [advanced scheduling patterns]
- Explore [complex sensor examples]
- Dive into [Declarative Automation best practices]

By understanding and effectively using these automation methods, you can build more efficient data pipelines that respond to your specific needs and constraints.

0 comments on commit c7425c7

Please sign in to comment.