Copyright (c) 2026 MindMesh Academy. All rights reserved. This content is proprietary and may not be reproduced or distributed without permission.
2.5.2. Schedules and Event-Based Triggers
💡 First Principle: Triggers determine when pipelines execute. Schedule triggers are like alarm clocks (run at specific times); event triggers are like motion sensors (run when something happens). Choose based on whether your process is time-driven or event-driven.
Scenario: Financial reports must run daily at 2 AM (schedule trigger). A data processing pipeline should run whenever new files arrive in the data lake (event trigger).
Trigger Types
| Trigger Type | Use Case | Example |
|---|---|---|
| Schedule | Time-based execution | Daily at 2 AM, hourly |
| Tumbling Window | Process data in time slices | Process each hour's data |
| Storage Event | React to file changes | New file in data lake |
| Custom Event | React to Event Grid events | External system notification |
⚠️ Exam Trap: Tumbling window triggers are for backfill and catch-up scenarios where each time slice must be processed independently. For simple daily execution, use a schedule trigger. Don't over-engineer simple scheduling requirements.
Written byAlvin Varughese
Founder•15 professional certifications