Preparing your workspaceloading the brief, studio & editor…

Loadingone moment…

extracttransformloadorchestrate

Scenario

2.SLA-awarealertingflow

Design an hourly pipeline for a team that depends on fresh data by a deadline: retry transient failures safely, monitor freshness, and escalate to the on-call the moment the SLA is at risk or missed — never fail silently.

This pipeline must answer

01Is the data fresh by its deadline — and who is paged the moment it isn’t?
02When a step fails transiently, does a retry fix it without double-counting?
03Can we see the pipeline’s health before a consumer complains?

Guardrails

Hourly freshness SLA
Retries must be idempotent
Include an observability/monitor and an escalation (alert) path, plus a dead-letter path
Avoid invalid cycles

Act 1 · Specify — answer all 8 and your spec flows0 / 8 answered

1Trigger & cadence

The data has an hourly deadline. What starts each run — and what starts the alarm?

In this pipeline the schedule and the SLA clock are two different things, and both need designing.

This choice changes which questions you are asked next — and the pipeline you end up drawing.

◆ What you are committing to on the canvas

What is the deadline for each hour’s data?
e.g.
“Hour H available by H+20” is checkable. “Hourly” only says how often you try.
- configTrigger `Runs` = daily / hourly — leaving it unset is what fails the freshness check
Is the SLA measured from the event, or from the run?
e.g.
From the event. A run that starts late still owes the same freshness to the consumer.
- nodeOrchestration & contracts → Scheduler trigger for a clock; Amazon MWAA, Step Functions, Dagster or Prefect when one step has to wait for another to finish

New to this?Batch vs Streaming vs Micro-batch

Edit your answer here✓ captured

Markdown: **bold** · *italic* · # heading · - bullet

Act 2 · Architect

Practice studio

Ctrl/Cmd + C copyCtrl/Cmd + V pasteCtrl/Cmd + Z undoDelete remove

40%

Design review

The reviewer reads your pipeline.

Run the review to check your architecture against this scenario — a valid DAG, a trigger for the freshness SLA, a transform stage, a quality gate before publish, and a failure path — then defend it in a short interview.

Desktop only

This scenario runs a full workspace — editor, canvas and results side by side. It needs a laptop or desktop to be usable. Open this page on a bigger screen to start building.

Read the library instead Back to modules

Preparing your workspaceloading the brief, studio & editor…

extracttransformloadorchestrate

Scenario

2.SLA-awarealertingflow

This pipeline must answer

01Is the data fresh by its deadline — and who is paged the moment it isn’t?
02When a step fails transiently, does a retry fix it without double-counting?
03Can we see the pipeline’s health before a consumer complains?

Guardrails

Hourly freshness SLA
Retries must be idempotent
Include an observability/monitor and an escalation (alert) path, plus a dead-letter path
Avoid invalid cycles

Act 1 · Specify — answer all 8 and your spec flows0 / 8 answered

1Trigger & cadence

The data has an hourly deadline. What starts each run — and what starts the alarm?

In this pipeline the schedule and the SLA clock are two different things, and both need designing.

This choice changes which questions you are asked next — and the pipeline you end up drawing.

◆ What you are committing to on the canvas

What is the deadline for each hour’s data?
e.g.
“Hour H available by H+20” is checkable. “Hourly” only says how often you try.
- configTrigger `Runs` = daily / hourly — leaving it unset is what fails the freshness check
Is the SLA measured from the event, or from the run?
e.g.
From the event. A run that starts late still owes the same freshness to the consumer.
- nodeOrchestration & contracts → Scheduler trigger for a clock; Amazon MWAA, Step Functions, Dagster or Prefect when one step has to wait for another to finish

New to this?Batch vs Streaming vs Micro-batch

Edit your answer here✓ captured

Markdown: **bold** · *italic* · # heading · - bullet

Act 2 · Architect

Practice studio

Ctrl/Cmd + C copyCtrl/Cmd + V pasteCtrl/Cmd + Z undoDelete remove

40%

Design review

The reviewer reads your pipeline.

Desktop only

This scenario runs a full workspace — editor, canvas and results side by side. It needs a laptop or desktop to be usable. Open this page on a bigger screen to start building.

Read the library instead Back to modules

SLA-aware alerting flow · Pipeline Builder scenario · D8LooP