A Lakeflow Job runs three ingestion tasks in parallel, and a final task named notify depends on all three. The team requires notify to post a run summary on every run, including runs where one ingestion task fails and runs where a task is skipped, and it must not be held back when a dependency ends in a state other than success. Which Run if condition on notify meets the requirement?
- AAt least one succeeded, which starts notify as soon as any dependency has succeeded and leaves it skipped on a run in which every ingestion task fails.
- BNone failed, which starts notify when every dependency has finished in a state other than failure and leaves it skipped as soon as one ingestion task fails.
- CAll succeeded, the default, which starts notify only when all three ingestion tasks have succeeded and leaves it skipped whenever one fails or is skipped.
- DAll done, which starts notify once every dependency has reached a terminal state, whether that state is success, failure or skipped. Correct
Why A is wrong: It loosens the default enough to survive a single failure, but it still needs one success, so the run where all three ingestion tasks fail is exactly the run that produces no summary.
Why B is wrong: This tolerates skipped dependencies, which is half of the requirement, but a single failed ingestion task suppresses the summary, and failures are the case the team most wants reported.
Why C is wrong: This is the setting already in place and the reason no summary appears on a bad night, since any non-successful dependency skips the dependent task.
Why D is correct: All done waits only for the dependencies to finish and ignores the outcome, which is the condition designed for cleanup and notification tasks that must run on every path.