Before you build anything, import a pipeline someone else built and take it apart. It's a three-node pipeline with one deliberate problem — finding and fixing it touches every area of the screen you'll use for the rest of the course.
Goal
The imported w1-2-tour pipeline running successfully, and a working map in your head of
where things live: the explorer, the palette, the canvas, the properties panel and the run log.
You'll need
- Odara running and signed in (level 1.1).
- The exercise files for this level. Unzip them on the machine where Odara runs — the import dialog browses the server's disk, not your browser's.
- About 12 minutes.
The archive holds w1-2-tour.json (the pipeline) and customers.csv (the data it reads).
Steps
1. Import the pipeline
In the Explorer tab on the left, right-click MY PIPELINES and choose
Import Pipelines. A file browser opens at your home folder; navigate to where you unzipped
the files, tick w1-2-tour.json and click Import (1).

Successfully imported 1 pipeline appears, and w1-2-tour shows up under MY PIPELINES.
Double-click it to open it in a tab.
2. Read the screen, left to right

- Left panel. Three tabs. Explorer lists what the project holds — pipelines and Maestros (orchestrations, World 5 onwards). Nodes is the palette you drag from. Resources holds reusable definitions — database connections, file schemas and context variables — that many pipelines can share.
- Canvas. The pipeline itself. Data flows left to right along the connections. The small controls in the bottom-left zoom and fit the view; the minimap in the bottom-right shows where you are on a big pipeline.
- Right panel. With nothing selected it describes the pipeline: its name, a description you can add, and counts of sources, transforms and targets. Click a node and it becomes Properties for that node.
- Top bar. The project you're in, the Editor menu, Execute, and on the right the Console toggle, Git, the API reference and your account.
Open the Editor menu. Editor is where you are; Schedule, Monitor and Documentation are Worlds 7 and 8 of this course.
3. Open the palette
Click the Nodes tab. Nodes are grouped in four sections — INGEST (sources), TRANSFORM, DELIVER (targets) and ORCHESTRATE (flow control) — and each section into folders like Files, Databases or Debug. The search box at the top filters them all.

The three nodes on the canvas came from INGEST ▸ Files ▸ CSV Source, TRANSFORM ▸ Data Processing ▸ SQL and DELIVER ▸ Debug ▸ Console. Go back to Explorer when you're done looking.
4. Execute it, and watch it fail
Click Console in the top-right to open the run log, then Execute.
The run fails. The canvas says Execution failed, the customers node gets a red Failed
badge, and the Console header counts the errors. Read the red lines:
customers failed: Connector error: CSV file not found: /replace/with/your/folder/customers.csv

That's the pattern for every failure in Odara: the badge tells you which node, the Console tells you why.
5. Fix it in Properties
Click the customers node. Its Properties show a File Path pointing at a folder that
doesn't exist. Replace it with the absolute path of the customers.csv you unzipped, then
click Preview Output to confirm Odara can read it.
Click the middle node, customers_by_country, and read its SQL. It counts customers per
country. input in the query is the data arriving from the node on its left.
6. Execute again
Execute. This time the canvas shows Completed in …ms, and the Console shows each node
finishing.
Find the [console] Output (click to expand) line and click it to see the result table.

Expected result
- The run completes with no failed node.
- The console table has 15 rows — one per country — and two columns,
countryandcustomers. - The first rows are
NL 42, thenMX 41andPL 41.
Common pitfalls
The import dialog doesn't show your Downloads folder. It browses the disk of the machine running Odara, starting at that user's home folder. If Odara runs on a server, copy the files there first.
You fixed the path but it still fails.
Check for quotes or a trailing space pasted along with the path, and that it's the full
absolute path including customers.csv. Preview Output fails fast with the same message
the run would, so use it before running again.
Only one row comes back, or the numbers look wrong. The SQL was edited. Delete the pipeline (right-click it under MY PIPELINES) and import the file again to get the original back.
What you built
Nothing new — you repaired someone else's pipeline, which is most of the job. From here on, when a run fails you already know the loop: find the red badge, read the Console, fix it in Properties, preview, run again.
Check yourself
One question, drawn from a larger bank. Get it right to pass.
The import dialog doesn't show the folder where your browser saved the download. Why?