Pipeline scheduling and triggers in MLOps - Mini Project: Build & Apply

Pipeline scheduling and triggers

📖 Scenario: You work as a machine learning engineer. You want to automate your ML pipeline to run regularly and also trigger it when new data arrives.This helps save time and keeps your models updated without manual work.

🎯 Goal: Build a simple Python script that simulates scheduling an ML pipeline to run every day at a fixed time and also triggers immediately when new data is detected.You will create a schedule, a trigger condition, and then run the pipeline accordingly.

📋 What You'll Learn

Create a variable called pipeline_name with the value 'daily_ml_pipeline'

Create a variable called schedule_time with the value '02:00' representing 2 AM daily

Create a variable called new_data_arrived set to True or False to simulate data arrival

Write an if statement that triggers the pipeline if new_data_arrived is True

Write an else statement that prints the scheduled run time of the pipeline

💡 Why This Matters

🌍 Real World

Automating ML pipelines saves time and ensures models stay updated by running at set times or when new data arrives.

💼 Career

Understanding pipeline scheduling and triggers is essential for ML engineers and DevOps professionals working with automated workflows.

1

Set up pipeline name

Create a variable called pipeline_name and set it to the string 'daily_ml_pipeline'.

MLOps

# Create the pipeline_name variable
# Your code here

Hint

Use the assignment operator = to set the variable.

2

Add schedule time variable

Create a variable called schedule_time and set it to the string '02:00' representing 2 AM daily.

MLOps

pipeline_name = 'daily_ml_pipeline'
# Create the schedule_time variable
# Your code here

Hint

Use a string to represent the time in 24-hour format.

3

Simulate new data arrival

Create a variable called new_data_arrived and set it to True to simulate that new data has arrived.

MLOps

pipeline_name = 'daily_ml_pipeline'
schedule_time = '02:00'
# Create the new_data_arrived variable
# Your code here

Hint

Use the boolean value True to indicate data arrival.

4

Trigger pipeline based on data arrival or schedule

Write an if statement that checks if new_data_arrived is True. If yes, print "Triggering {pipeline_name} due to new data." using an f-string. Otherwise, print "Scheduled run of {pipeline_name} at {schedule_time}." using an f-string.

MLOps

pipeline_name = 'daily_ml_pipeline'
schedule_time = '02:00'
new_data_arrived = True
# Add if-else to trigger pipeline or show schedule
# Your code here

Hint

Use if new_data_arrived: and f-strings for printing.

Practice

1. What is the main purpose of pipeline scheduling in MLOps?

easy

A. To store pipeline logs for debugging

B. To manually start pipelines whenever needed

C. To run tasks automatically at specific times without manual intervention

D. To create new machine learning models from scratch

Solution

1. Step 1: Understand pipeline scheduling

   Pipeline scheduling is designed to run tasks automatically at set times, like daily or hourly, without needing a person to start them.

2. Step 2: Compare options

   Only To run tasks automatically at specific times without manual intervention describes automatic running at specific times. Other options describe manual actions or unrelated tasks.

3. Final Answer:

   To run tasks automatically at specific times without manual intervention -> Option C

4. Quick Check:

   Pipeline scheduling = automatic timed runs [OK]

Hint: Scheduling means automatic runs at set times [OK]

Common Mistakes:

• Confusing scheduling with manual triggering
• Thinking scheduling stores logs
• Assuming scheduling creates models directly

2. Which of the following is a correct cron expression to schedule a pipeline to run every day at 3 AM?

easy

A. 3 0 * * *

B. 0 3 * * *

C. * 3 * * *

D. 0 0 3 * * *

Solution

1. Step 1: Understand cron format

   Cron syntax is: minute hour day month weekday. To run at 3 AM daily, minute=0, hour=3, day/month/weekday=any (*).

2. Step 2: Match expression

   0 3 * * * "0 3 * * *" means minute 0, hour 3, every day. Others have wrong order or extra fields.

3. Final Answer:

   0 3 * * * -> Option B

4. Quick Check:

   Minute=0, Hour=3 daily = 0 3 * * * [OK]

Hint: Cron: minute hour day month weekday; 3 AM is '0 3 * * *' [OK]

Common Mistakes:

• Swapping hour and minute fields
• Adding extra fields in cron
• Using '*' in wrong positions

3. Given this pipeline trigger configuration snippet:

{
  "trigger": {
    "event": "data_arrival",
    "filter": {
      "file_type": "csv"
    }
  }
}

What happens when a new JSON file arrives in the data folder?

medium

A. The pipeline does not run because the file type is not CSV

B. The pipeline runs because any new file triggers it

C. The pipeline runs only if the JSON file is large

D. The pipeline runs but ignores the file type

Solution

1. Step 1: Analyze trigger filter

   The trigger listens for 'data_arrival' events but only runs if the file type is 'csv'.

2. Step 2: Apply to JSON file

   A JSON file does not match the 'csv' filter, so the pipeline will not run.

3. Final Answer:

   The pipeline does not run because the file type is not CSV -> Option A

4. Quick Check:

   Filter file_type=csv blocks JSON files [OK]

Hint: Triggers with filters run only on matching events [OK]

Common Mistakes:

• Ignoring filter conditions
• Assuming any file triggers pipeline
• Confusing event type with file type

4. You wrote this cron expression to schedule a pipeline every hour:

60 * * * *

Why does the pipeline never run?

medium

A. Because the hour field is missing

B. Because cron requires seconds field

C. Because the asterisks are misplaced

D. Because 60 is not a valid minute value in cron syntax

Solution

1. Step 1: Check minute field validity

   Cron minute values must be 0-59. '60' is invalid and causes no runs.

2. Step 2: Confirm other fields

   The hour and other fields are correct as '*', meaning every hour/day. The error is only the minute value.

3. Final Answer:

   Because 60 is not a valid minute value in cron syntax -> Option D

4. Quick Check:

   Minute must be 0-59; 60 is invalid [OK]

Hint: Minutes in cron go 0-59, never 60 [OK]

Common Mistakes:

• Using 60 as minute value
• Thinking cron needs seconds field
• Misplacing asterisks

5. You want a pipeline to run automatically when new data arrives and also every Sunday at midnight. Which setup correctly combines scheduling and event triggers?

hard

A. Use a cron schedule '0 0 * * 0' and an event trigger for 'data_arrival' together

B. Use only a cron schedule '0 0 * * 0' because event triggers conflict with schedules

C. Use only an event trigger for 'data_arrival' and manually run on Sundays

D. Use a cron schedule '0 0 * * 7' and ignore event triggers

Solution

1. Step 1: Understand combined triggers

   Pipelines can have both cron schedules and event triggers to run on different conditions.

2. Step 2: Verify cron expression for Sunday midnight

   '0 0 * * 0' runs at midnight on Sundays (0 or 7 can represent Sunday, but 0 is standard).

3. Step 3: Confirm event trigger for data arrival

   Adding an event trigger for 'data_arrival' ensures pipeline runs when new data arrives.

4. Final Answer:

   Use a cron schedule '0 0 * * 0' and an event trigger for 'data_arrival' together -> Option A

5. Quick Check:

   Combine cron and event triggers for full automation [OK]

Hint: Combine cron and event triggers for multiple run conditions [OK]

Common Mistakes:

• Thinking schedules and triggers cannot coexist
• Using wrong cron day for Sunday
• Ignoring event triggers for data arrival