# Three pipelines on the canvas have schedule mismatches the section just named

Canonical URL: <https://datadriven.io/problems/three-pipelines-on-the-canvas-have-schedule-mismatches-the-s-663c1fc4>

Domain: Pipeline Design · Difficulty: medium

## Problem

Three pipelines on the canvas have schedule mismatches the section just named. The monthly close pipeline runs at midnight on the 1st (cron is correct: wall-clock alignment with a calendar moment). The webhook-driven payments pipeline polls Stripe via cron every 15 minutes, but Stripe emits webhooks; an event trigger fires precisely when there is work, not on a fixed cadence. The Kafka offset poller runs every 5 minutes via cron; the wall-clock time doesn't matter, only the gap between runs (an interval schedule would be more idiomatic). Apply the schedule-selection framing this section just taught and re-tag each pipeline with the right schedule form. Tag the monthly close as Cron (correct as-is). Tag the webhook-driven pipeline as Event-Trigger (or Sensor, Webhook, or Dataset) so it fires on Stripe webhook arrival. Tag the Kafka poller as Interval so it runs every N units without anchoring to a wall-clock time.

## Related

- [All practice problems](https://datadriven.io/problems)
- [Mock interview mode](https://datadriven.io/interview/three-pipelines-on-the-canvas-have-schedule-mismatches-the-s-663c1fc4)
- [System Design Interview Questions](https://datadriven.io/data-engineering-system-design)
- [Data Engineering Interview Prep Guide](https://datadriven.io/data-engineer-interview-prep)
- [Daily Challenge](https://datadriven.io/daily)

---

Source: DataDriven (https://datadriven.io). 100% free data engineering interview prep. Live code execution against Postgres 16, Python 3.11, and Spark sandboxes. No paywall, no premium tier, no signup gate.