Publishing freezes the pipeline definition into an identifiable version. Publishing does not read the source, does not write to the destination, and does not turn on the schedule.
Before you start#
- Be the workspace owner (Pipelines is the owner's area).
- Have a saved, authorized connection, or use the file flow.
- Subscription in good standing: running is an expensive action and goes through the access check.
Step by step#
1. Open the pipeline
In ETL/ELT → Pipelines, use New pipeline to create a new pipeline, or open an existing one. Starting from a connection that is already saved, the shortcut is Build extraction, on the connection's card in ETL/ELT → Connections.
2. Review the definition
Check the source, selected data, transformations, load mode, and destination. A draft can be saved without being complete — it does not show up as published and cannot be run.
3. Publish
Use Publish (schedule off). The button label is literal: it is what happens.
4. Read the confirmation
The product responds: "Pipeline published as version 1 — the SCHEDULE was left OFF and nothing was run." From then on, Turn on schedule and Run now become available in the pipeline's publishing panel.
Expected result#
- There is an identifiable version of the definition (the first one is version 1).
- The schedule is off.
- No rows were read, written, or charged.
- The event is recorded in the audit log.
Updating a pipeline that is already active#
Republishing a pipeline that already has an active schedule does not silently turn off the schedule. The screen tells you the effect on the existing schedule before you confirm. If the stated effect is not what you want, cancel and adjust.
What the version freezes
The version freezes the definition — what to read, transform, and write. It does not freeze the credential: the pipeline points to the connection, so changing the password in the connection applies to every version and every pipeline that uses it.
If something goes wrong#
| Symptom | What to check | Next action |
|---|---|---|
| Publishing blocked | The validation flagged in the review | Fix the indicated item; don't invent a dependency or credential to move forward |
| I published and it didn't run | The schedule status | That is the expected behavior — use Turn on schedule or Run now |
| I published and the schedule disappeared | The effect message shown on republishing | Turn it back on with Turn on schedule; the product never turns it off without telling you |
| "Subscription … is blocked" | The workspace's billing status | Settle it in Administration → Plans |
Limits and costs#
- Publishing: R$ 0. There is no reading from the source and no writing to the destination.
- Running consumes cloud resources — see cost, limits, and security.
- We don't publish publishing or run times: they depend on the volume of your data and on the source. There is no published measurement.
Next task#
Last review: 2026-09-16.