From ec5c6ab9de6a782aa262113b72843114434be133 Mon Sep 17 00:00:00 2001 From: nikki everett Date: Thu, 19 Dec 2024 21:03:29 -0600 Subject: [PATCH] one last link fix Signed-off-by: nikki everett --- docs/docs-beta/docs/guides/automate/about-automation.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/docs/docs-beta/docs/guides/automate/about-automation.md b/docs/docs-beta/docs/guides/automate/about-automation.md index 908df0c7f6ba5..ccfd35b0a24ec 100644 --- a/docs/docs-beta/docs/guides/automate/about-automation.md +++ b/docs/docs-beta/docs/guides/automate/about-automation.md @@ -25,8 +25,6 @@ as the schedule is processed. Schedules were one of the first types of automation in Dagster, created before the introduction of Software-Defined Assets. As such, you may find that many of the examples can seem foreign if you are used to only working within the asset framework. -For more on how assets and ops inter-relate, read about [Assets and Ops](/guides/build/create-asset-pipelines/assets-concepts#assets-and-ops) - The `dagster-daemon` process is responsible for submitting runs by checking each schedule at a regular interval to determine if it's time to execute the underlying job.