Skip to content

Commit 9f74416

Browse files
committed
some fixes
1 parent 0142585 commit 9f74416

File tree

1 file changed

+20
-9
lines changed

1 file changed

+20
-9
lines changed

articles/machine-learning/how-to-schedule-pipeline-job.md

Lines changed: 20 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -71,7 +71,7 @@ The code examples in this article are excerpts from the [Working with Schedule](
7171

7272
# [Studio UI](#tab/ui)
7373

74-
To create a schedule for an Azure Machine Learning v2 pipeline job, open the pipeline page for that job.
74+
To create a schedule for an Azure Machine Learning v2 pipeline job in the studio UI, open its pipeline detail page.
7575

7676
---
7777

@@ -95,7 +95,7 @@ You must or can provide the following schedule parameters:
9595

9696
# [Studio UI](#tab/ui)
9797

98-
To open the schedule creation wizard, select **Schedule** > **Create new schedule**.
98+
To open the schedule creation wizard, select **Schedule** > **Create new schedule** at the top of the page.
9999

100100
:::image type="content" source="./media/how-to-schedule-pipeline-job/schedule-entry-button.png" alt-text="Screenshot of the jobs tab showing the Create new schedule button selected." lightbox= "./media/how-to-schedule-pipeline-job/schedule-entry-button.png":::
101101

@@ -142,6 +142,7 @@ After you create the schedule YAML, use the following command to create the sche
142142
# This action creates related resources for a schedule. It takes dozens of seconds to complete.
143143
az ml schedule create --file simple-pipeline-job.yml --no-wait
144144
```
145+
145146
# [Python SDK](#tab/python)
146147

147148
The following Python code creates the schedule you defined:
@@ -186,7 +187,7 @@ You must or can provide the following schedule parameters:
186187

187188
# [Studio UI](#tab/ui)
188189

189-
To define a cron-based schedule, select **Cron expression** instead of **Recurrence** on the **Basic settings** screen.
190+
To define a cron-based schedule, select **Cron expression** instead of **Recurrence** on the **Basic settings** screen for the schedule.
190191

191192
---
192193

@@ -220,7 +221,10 @@ Only the **Name** property requires you to enter a value. If you don't specify a
220221

221222
After you create the schedule YAML, use the following command to create the schedule via CLI:
222223

223-
:::code language="azurecli" source="~/azureml-examples-main/cli/schedules/schedule.sh" ID="create_schedule":::
224+
```azurecli
225+
# This action creates related resources for a schedule. It takes dozens of seconds to complete.
226+
az ml schedule create --file simple-pipeline-job.yml --no-wait
227+
```
224228

225229
# [Python SDK](#tab/python)
226230

@@ -242,7 +246,7 @@ Sometimes you might want the jobs triggered by schedules to have different confi
242246

243247
When you define a schedule, you can change the `settings`, `inputs`, or `outputs` to use when running the pipeline job. You can also change the `experiment_name` of the triggered job.
244248

245-
The following schedule definition changes the settings of the existing job.
249+
The following schedule definition changes the settings of an existing job.
246250

247251
:::code language="yaml" source="~/azureml-examples-main/cli/schedules/cron-with-settings-job-schedule.yml":::
248252

@@ -338,11 +342,11 @@ Select a schedule name to show the schedule detail page, which contains the foll
338342
:::code language="azurecli" source="~/azureml-examples-main/cli/schedules/schedule.sh" ID="update_schedule":::
339343

340344
> [!NOTE]
341-
> To update more than just tags and description, use `az ml schedule create --file update_schedule.yml`.
345+
> To update more than just tags and description, use `az ml schedule create --file simple_cron_job_schedule.yml`.
342346
343347
# [Python SDK](#tab/python)
344348

345-
[!Notebook-python[] (~/azureml-examples-main/sdk/python/schedules/job-schedule.ipynb?name=create_schedule)]
349+
[!Notebook-python[] (~/azureml-examples-main/sdk/python/schedules/job-schedule.ipynb?name=enable_schedule)]
346350

347351
# [Studio UI](#tab/ui)
348352

@@ -369,7 +373,7 @@ Once you set up a schedule to do regular retraining or batch inference on produc
369373

370374
1. Select **Review + Update** to review the schedule settings, and then select **Review + Update** again to finish the update.
371375

372-
After the update completes, you can view the new job definition in the schedule detail page. The schedule now triggers different jobs.
376+
After the update completes, you can view the new job definition in the schedule detail page. The schedule now triggers the new job.
373377

374378
---
375379

@@ -381,6 +385,8 @@ After the update completes, you can view the new job definition in the schedule
381385

382386
# [Python SDK](#tab/python)
383387

388+
The following code returns `False`:
389+
384390
[!Notebook-python[] (~/azureml-examples-main/sdk/python/schedules/job-schedule.ipynb?name=disable_schedule)]
385391

386392
# [Studio UI](#tab/ui)
@@ -397,7 +403,12 @@ You can disable schedules from the **All schedules** tab or disable the current
397403

398404
# [Python SDK](#tab/python)
399405

400-
[!Notebook-python[] (~/azureml-examples-main/sdk/python/schedules/job-schedule.ipynb?name=enable_schedule)]
406+
The following code returns `True`:
407+
408+
```python
409+
job_schedule = ml_client.schedules.begin_enable(name=schedule_name).result()
410+
job_schedule.is_enabled
411+
```
401412

402413
# [Studio UI](#tab/ui)
403414

0 commit comments

Comments
 (0)