Skip to content

Automatic translation — the Portuguese version is the reference. View in Portuguese

Updated on 2026-10-03

Orchestration

The product that defines, publishes, schedules, runs, and recovers the pipelines that bring in your data.

On this page (4)

Orchestration is what happens in the ETL/ELT group of the menu (Connections · Pipelines · Runs). This is where a pipeline becomes a published version, gets (or doesn't get) a schedule, is run, and, when it fails, is recovered.

The separation matters, and the product takes it seriously:

ObjectWhat it isWhere it lives
ConnectionAuthorized access to a source: address, parameters, and the encrypted credential.ETL/ELT → Connections
PipelineThe definition of what to read, transform, and write. It points to a connection; it never copies the credential.ETL/ELT → Pipelines
VersionThe immutable snapshot of the definition at the moment of publishing.The pipeline's publishing panel
ScheduleThe rule for when to run. You choose the time in Brasília time; it stays off until you turn it on.Pipeline schedule card
RunA concrete round of that version, with tasks, attempts, and logs.ETL/ELT → Runs

Publishing is not running

The first publication of a pipeline creates version 1 and leaves the schedule off. Nothing is read, written, or charged at that moment. Turn on schedule and Run now are two separate actions, each with its own click.

Guides for this product#

Day-to-day operations (articles in Data)#

These topics belong to orchestration, but the articles have lived in Data since the first version of the documentation. The addresses still work — nothing was moved, nothing broke:

Before you start#

  • You must be the workspace owner to see Pipelines and Runs. People who only consume BI don't see these screens.
  • Running a pipeline is an expensive action: with the subscription overdue, suspended, or canceled, the run is blocked with an explicit message and a link to Plans. See Suspension.
  • The connection test goes out from the application server; the pipeline executor runs on another network, with another outbound IP. Allow both on your network.

If something goes wrong#

SymptomNext action
I published and nothing happenedThat is the expected behavior: use Turn on schedule or Run now.
The schedule didn't fireCheck that it is on (the Schedule on badge) and the Brasília time shown on the pipeline.
The run failedOpen the task, then the attempt, then the log — in that order.
I reran and it duplicatedCheck the scope chosen in the recovery and the pipeline's load mode.
Expired credentialFix it in the connection, once. Every pipeline that points to it starts using the new value.

Last review: 2026-09-16. Examples use the fictitious workspace Comércio Aurora Ltda (aurora). No customer data appears in this documentation.

Related links