A Lakeflow Job runs every 30 minutes on a schedule, and each run takes about 40 minutes. The team notices that some scheduled runs never execute: while a previous run is still active, the new run appears as skipped. The job was created with the Jobs REST API, and queueing was not enabled. What is the cause, and how can the team fix it?

1. A. The scheduler enforces a 10-second minimum interval between runs and drops anything closer; the schedule must be shortened 💬 A
2. B. Maximum concurrent runs defaults to 1 and extra runs are skipped — raise it, or enable queueing ✓ B
3. C. Scheduled jobs cannot overlap by design; convert the trigger to a continuous trigger to serialize the runs 💬 C
4. D. Skipped runs indicate an invalid cron expression; the schedule must be rewritten in Quartz cron syntax 💬 D

Reveal answer

Correct answer: Maximum concurrent runs defaults to 1 and extra runs are skipped — raise it, or enable queueing

Reference: https://docs.databricks.com/aws/en/jobs/configure-job