Scheduled URL Load
The URL tab of Upload can load a page on its own, at whatever time you set. The Schedule button, next to Load URL, saves the load you just configured — same URL, same context, same options — for a specific date or for a recurrence. It is how you keep a legislation, ordinance or case-law context up to date with the official source without anyone remembering to reload it.
The Datta Scheduler fires it, the same clock that runs DATTA Extract loads and scheduled batch screening. It is a scheduler belonging to the platform itself, with the same guarantees: one execution per slot, a record of what was missed while the platform was down, and the same calendar.
How to schedule
- Open Process › Upload, tab URL.
- Pick the context that receives the load.
- Paste the URL (a law from Planalto, an ordinance from the Federal Revenue rules portal, CARF case law) and, if you want, the article filter and the Refresh the whole base option — they travel with the schedule.
- Click Schedule.
- In the dialog, pick the recurrence:
| Recurrence | When to use |
|---|---|
| Once | a specific date and time. Runs once and the schedule ends itself |
| Every | free interval — every 6 hours, every 2 days |
| Daily | one or more times, every day |
| Weekly | chosen weekdays at the given times — the most common for legislation |
| Monthly | chosen days of the month. A day that does not exist in a month is skipped |
- Check the next executions listed in the dialog — they are computed by the server, with the same arithmetic the scheduler will use.
- Save schedule.
The schedule shows up at the top of the tab, under Scheduled URL loads, with the recurrence in plain language, the context, the URL and the next execution.
What travels with it — the same as the Load URL button
The schedule stores exactly what the Load URL button would send at that moment: URL, context, article filter and the Refresh the whole base option. At the scheduled time the platform performs the same load a click would: the legislation page is read again, the article graph is updated and the texts are reindexed.
To keep a legislation context current, the usual choice is a weekly load with Refresh the whole base on: amended provisions get the new wording and the amendment note; unchanged ones are kept.
To change the URL, the context or the options of an existing schedule, use Edit on its card: the tab fields are filled with what is stored, and the dialog saves whatever is on screen.
Pause, resume, edit and remove
| Action | What it does |
|---|---|
| Pause | keeps the schedule and stops firing. Nothing is deleted |
| Resume | puts it back on the clock; the next execution applies again |
| Edit | reopens the dialog to change the recurrence (and the URL/options on screen) |
| Remove | deletes the schedule for good. What was already loaded is preserved |
A pause applies immediately and on every replica of the platform: the stored state decides each firing and is re-read at every occurrence.
What happens at the scheduled time
The scheduled load starts exactly as if you had clicked Load URL: the task appears in the Execution History and can be followed there. If the official source is down or unreachable from the platform, the occurrence is recorded as a failure and the schedule's retry policy decides what to do — the schedule is not removed.
If the platform was down at the time, the missed execution is recorded, and your choice in the dialog applies: "Skip the execution" (default) or "Run once when back".
Where else the scheduled load shows up
It is a row of the platform agenda, so it also appears in DATTA Extract › Scheduler:
- Calendar — next to loads and screenings, labelled URL load.
- Engine — in the list of what the clock will fire, with next execution, last firing and missed executions. Platform administrators can pause it there.
Permissions
| Action | Permission |
|---|---|
| See scheduled loads | DOCUMENT_VIEW or DOCUMENT_UPLOAD |
| Create, edit, pause, resume and remove | DOCUMENT_SCHEDULE |
| Pause/resume from the Scheduler Engine tab | PLATFORM_ADMIN |
The default advanced user role receives DOCUMENT_SCHEDULE — whoever loads URLs and refreshes contexts also schedules them. The permission is deliberately separate from DOCUMENT_UPLOAD: loading a URL is an observed act, with someone at the screen; scheduling leaves the platform re-reading the official source and rewriting the context on its own, indefinitely.