Skip to content

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

Updated on 2026-10-03

Schedule, time zone, and pause

Turning on the schedule, running now, and pausing are distinct actions; the schedule time is chosen and shown in Brasília time.

On this page (7)

Three different actions, three different buttons:

ActionButtonWhat it does
Turn on repetitionTurn on scheduleStarts firing the run at the configured time. It doesn't run anything right away.
Run onceRun nowCreates one immediate run of the published version. It doesn't turn on the schedule.
Stop repetitionPause scheduleTurns off repetition and clears the next time. The pause persists — it doesn't come back on its own at the next publication or the next day.

The time zone, without ambiguity#

Since October 3, 2026, you choose and read the schedule in Brasília time — the same as your company's clock:

  • On the Pipeline schedule card, the field is labeled Time (Brasília), with the hint "Prefer the early hours: the source system is usually less busy."
  • The schedule summary appears as, for example, Scheduled · Daily at 02:00 (Brasília).
  • While building the pipeline, the Next five runs box shows the upcoming triggers before you turn anything on.
  • On the Runs screen, dates and times are also in Brasília time.

Under the hood, the product stores the instant in UTC — that's why the recovery panel, when it asks for a period, says From day (inclusive, UTC).

Run time ≠ processed period

The schedule time says when the pipeline runs. The data range it processes is defined by the load mode (watermark, partition, window). See incremental ingestion and backfill.

Before you start#

  • The pipeline must be published (a version exists).
  • Be the workspace owner.
  • Subscription in good standing: running is an expensive action and is blocked when overdue, suspended, or canceled.

Step by step#

  1. 1. Open the pipeline

    In ETL/ELT → Pipelines, open the published pipeline.

  2. 2. Set the time

    On the Pipeline schedule card, click Edit schedule, choose Every day, at a set time, and enter the Time (Brasília). Save with Save schedule — saving only changes the time, it doesn't turn anything on.

  3. 3. Turn it on

    Use Turn on schedule. The screen starts showing the next time.

  4. 4. (Optional) Run once now

    Use Run now if you want an immediate load. Review the context, version, and destination before confirming.

  5. 5. To stop

    Use Pause schedule. The next time is cleared and the event is recorded in the audit log.

Expected result#

  • With the schedule on, the screen shows the next time, in Brasília time.
  • With the schedule paused, the screen shows the schedule as inactive and there is no next time.
  • Turning on the schedule does not trigger a historical recovery. Earlier periods are only processed if you explicitly ask for a backfill.

If something goes wrong#

SymptomWhat to checkNext action
It ran three hours earlier/later than expectedWhether the time was set thinking in UTC (as the field worked until October 3, 2026)Open Edit schedule and check the Time (Brasília)
Schedule on and nothing ranBilling status, the capability's kill switch, concurrency limitCheck Plans and the message on the runs screen
I paused and it came back on its ownWhether someone republished and turned it back onThe pause persists in the product; check the audit log
I just want a test load—Use Run now without turning on the schedule

Limits and costs#

  • Turning the schedule on or pausing it: R$ 0.
  • Each run consumes cloud resources, charged in credits.
  • There is no promise of run time: it depends on volume and on the source.

Next task#


Last review: 2026-10-03.

Related links