In ETL/ELT → Runs (the menu was called DAGs until October 3, 2026) you find the history. Inside a run there are four levels, and they don't mean the same thing:
| Level | What it is |
|---|---|
| DAG | The pipeline's design: the tasks and the dependencies between them. |
| Run | A concrete round of the DAG, with start, end, and result. |
| Task | A step inside the run (extract, transform, materialize). |
| Attempt | One try at that task. A task that failed and was retried has more than one. |
The log belongs to an attempt, not to the whole run. Reading the log of the wrong attempt is the most common cause of a wrong conclusion.
Before you start#
- Be the workspace owner.
- Have at least one run created (by the schedule or by Run now).
Step by step#
1. Open the pipeline in the list
In ETL/ELT → Runs, click Open on the pipeline's row (or use the "Open with the last run already selected" icon). Times are shown in Brasília time.
2. Choose the run
In Grid — click a run or a task, or in the Run selector in the header, choose the run by its start time. Don't compare two runs just because the pipeline name is the same.
3. Select the task
In the grid or on the Graph tab, click the task you care about. The first tab, Run, is renamed Task. To go back, use Back to the whole run.
4. Select the attempt
If the task has more than one attempt, choose the right one in the Attempt selector.
5. Open the Logs tab
The tabs are Run (or Task) · Graph · Logs · Definition. The log shown is the one for the selected attempt; the Definition is the one from the version that ran in that run.
Expected result#
You can say, without guessing: which version ran, when it started (with time zone), which task failed, on which attempt, and with which message.
If something goes wrong#
| Symptom | What to check | Next action |
|---|---|---|
| The log doesn't match the error | Whether the selected attempt is the right one | Switch attempts before drawing conclusions |
| Task "pending" for a long time | Concurrency limit, a dependency not yet finished | Check the graph: a task only runs when the previous ones finish |
| Green run, empty dashboard | Destination, materialization, and the dashboard's binding | The DAG finishing does not guarantee that every dashboard has already refreshed — see view a dashboard |
| Authentication failure | The referenced connection | Fix it in the connection; don't re-enter the password inside the pipeline |
| Schema failure | Input contract and mapping | See pipeline and schema troubleshooting |
Limits and costs#
- Viewing runs, tasks, attempts, and logs: R$ 0.
- Retention of logs and events follows the governance and LGPD policy.
Next task#
- Recover from a failure
- Runs screens — the exact name of each button
- Scheduling, retry, and DLQ
- Recover deleted or overwritten data (7-day time travel)
Last review: 2026-10-03.