Scheduler — Calendário tab

"When does this load run?" was a question only a six-field technical pattern answered — and 0 30 4 * * * answers nothing for whoever opens the screen. The Calendário (calendar) tab shows, on one calendar, what already ran and what will run, and lets you build the repetition by picking the shape and the time.

It lives under DATTA Extract › Scheduler, tab Calendário.

One screen, three tabs

The Scheduler brings together, on a single screen, everything that answers when and how loads run:

They used to be three separate menu destinations (two under DATTA Extract and one under Configurar). It was the same question split three ways: whoever saw a failure on the calendar had to leave the screen to open the run detail, and whoever needed to pause the load left again for another area of the platform.

Old addresses still work. view=pipeline-agenda, view=pipeline-monitor and view=datta-scheduler open the Scheduler already on the matching tab — saved links, bookmarks and old shortcuts do not break.

The calendar

Each day of the month shows three counts, when they exist:

Click a day to open the side panel with the list. Click a run to see the detail: duration, rows read and written, warnings, the error (with the stage where it happened) and how much each flow node processed.

The filters at the top narrow by package and by status.

The predicted time is the real time. The calendar's forecast is computed by the same code that fires the run — it is not a parallel estimate. If the screen says 04:30, 04:30 is what the scheduler will use.

Building the repetition

In a day's panel, the Editar agendamento button opens the editor.

The same editor, reachable from three places. It is not exclusive to this tab: the Agendar button on the ETL Designer toolbar and the Agendar execução action in each package's menu in the gallery open exactly this dialog — same fields, same preview, same write. Whoever has just built the flow schedules it without coming here to hunt the package on the calendar. See DATTA Extract §4.5.

Pick the repetition shape:

Those four, and only those. There is no field for typing a technical scheduling pattern anymore: whoever builds the repetition picks the shape and the time, and the platform handles the rest. Packages created before that keep working — see "Legacy schedule" below.

While you build it, the preview lists the next runs. An invalid schedule (weekly with no day marked, time outside the HH:mm format, inverted window) shows the explanation in Portuguese and the save button stays disabled — nothing is stored half-done.

If the time passes while the platform is down

The editor has a second choice, right below the repetition:

Either way, the miss is always recorded. Before, a lost window simply did not happen and nothing pointed at it — whoever found out was the data consumer, a day later. Each package's misses are listed on the Motor tab, with the time and what the platform did.

"Run once" replays one load, not one per missed time: three days of window do not become three identical runs in a row, which would take the destination down instead of catching it up.

Legacy schedule

A package created before the visual editor — including the packages that ship with the platform — opens normally:

• When the legacy repetition has an equivalent among the four shapes, the editor opens with the fields already filled and says so: "read as every day at 04:30 — the times are exactly the same". Nothing changes in what runs.
• When it does not (a pattern the screen cannot draw), the package keeps firing as always and the editor shows "Agendamento personalizado" (custom schedule) with the next runs beside it. Picking one of the four shapes replaces the legacy schedule — and only when you save.

In neither case does the platform show the technical pattern on screen.

What the repetition solves and the legacy format did not

• Free interval. "Every 90 minutes" did not fit the legacy format, which only accepted divisors of the hour.
• Several times with no side effect. Choosing 08:30 and 14:00 fires at exactly those two. The legacy equivalent would also fire at 08:00 and 14:30 — the cross product of minutes and hours.
• Day 31. A monthly schedule on day 31 simply does not occur in February; it does not slide to the 28th nor to March 1st.

Validity window

The (optional) date fields bound when the schedule applies. After the end date the package stops by itself — nobody has to remember to switch off a seasonal or migration load.

History

Every run that ends — completed, failed or cancelled — is stored durably and shows up in three places:

1. On this calendar, on the day it happened, with the full detail;
2. On the *Job Monitor* tab, in the history table, with search, status filter, sorting and pagination;
3. In the platform's background executions panel, alongside triage and uploads, as an execution of type etl. See Full Execution History.

The history survives platform restarts and upgrades, and can be filtered by period — unlike the monitor's operational state, which is a window into what is happening right now.

Frequently asked

Where did the "Agenda de Cargas" screen go? It became the Calendário tab of this screen. The content is the same — calendar, day panel, repetition editor — and the old addresses open the Scheduler already on it.

My old packages use the technical scheduling format. Do I have to rewrite them? No. They keep working exactly as they are and already appear on the calendar. The editor reads the legacy repetition and shows the equivalent shape; what has no equivalent shows up as "Agendamento personalizado" (custom schedule), with the next runs beside it. Rewriting is optional, and only happens if you pick one of the four shapes and save.

A run did not happen. How do I find out? Every missed window is recorded, with the time that was missed and what the platform did (skipped or replayed). If you want it replayed automatically, mark "Executar uma vez ao voltar" in the package editor.

I changed the schedule and nothing appeared on the calendar. Check the validity window: if the end date has passed there is no next run, and the screen says so. Also check that the package is active — a paused or archived package does not schedule. The Motor tab shows each package's state and explains, next to the repetition, why a schedule yields no next run.

A run disappeared from the history? The history starts at the first run after the upgrade that brought this screen; earlier runs remain in the monitor, but were not imported.

I scheduled it from the ETL Designer and I do not see it here. Refresh the calendar: the schedule is written to the same package, and the tab reads the preview when it loads. If it still does not show up, check the validity window and whether the package is active — the same two causes as the previous question.

I do not see the edit-schedule button. Editing the schedule requires the permission to edit the package (PIPELINE_CREATE, or an administrator profile). Without it the button does not appear — see RBAC.

I cannot pause a package from the Motor tab. Pausing and resuming are platform operations and require an administration permission — see Motor. The Calendário and Job Monitor tabs do not depend on that permission.