Scheduled Jobs

Administrators and Power Users can open Server Administration Page from User Button, then select Scheduled Jobs under System Monitoring.

Use the table to inspect saved backup, RDF import, RDF export, Explorer publication and Problems & Suggestions report jobs. Search, status and job-type filters, pagination and Include deleted jobs help locate a job.

Select a row to inspect its saved configuration and execution history. The details panel displays its name, job type, schedule and creator. Deleted jobs retain their history. Closing the browser does not stop saved schedules.

Create and manage jobs

Select New Job, choose an available job type, enter a name and schedule, and complete its settings. Select Create Job to enable the schedule.

  • Backup: choose local server storage or a configured S3 bucket and the number of successful archives to retain.

  • File Import: choose a writable collection and an existing RDF source in a workspace project or configured S3 bucket.

  • File Export: choose a readable collection, Turtle or TriG format, and workspace or configured S3 storage.

  • Publish: select collections and a configured, licensed Explorer connection.

  • P&S Report: select a collection for a retained Problems & Suggestions report.

Choose an offered interval, daily, weekdays, weekly or monthly recurrence. Times use the server’s time zone, which the history cleanup dialog shows. New jobs default to daily at 2:00 AM; intervals have a five-minute minimum and initially select 15 minutes. A monthly day absent from a month is skipped. Check Next run after saving, particularly around daylight-saving changes.

Select a row to edit its settings, then Save. Background refresh preserves unsaved edits until you save or discard them. Editing does not change the creator; executions use the creator’s current permissions.

Pause stops future runs. Resume checks current permissions and configuration. Delete Job removes future scheduling after confirmation and retains history. Neither pause nor delete undoes work already started. Unavailable destinations must be configured before creating or resuming a job; pause and delete remain available. A job whose schedule could not be registered is saved paused, and its details show the reason until it is resumed.

Inspect results and failures

The table shows each job’s schedule, state, last and next run, and latest output. Jobs with upcoming runs appear first, soonest first. Jobs without a next run follow, ordered by their most recent run, with never-run jobs last in that group. Use Paused schedules (any run status) to find paused schedules regardless of their latest execution outcome.

History entries show outcomes, diagnostics and available outputs:

  • Completed means the operation finished.

  • Failed includes a diagnostic explaining the failure.

  • Interrupted means completion could not be established. Check the target collection or remote system before retrying; some work may already have completed.

Select an available output to open or download it. Missing, deleted or denied outputs are identified when requested. Backup downloads require Administrator access. A retained S3 output refers to its original object, so an old link does not download a replacement file.

Clean up history

Select Cleanup old history to remove old history entries. Choose a job and an Older than date. Administrators can also choose All jobs. Entries of runs that finished before midnight on that date, in the displayed server time zone, are eligible.

Select Preview cleanup to see how many entries are eligible, then Remove history to delete them. Cancel leaves the history unchanged.

Cleanup removes only the history entries of finished runs. Running jobs, job definitions, schedules and output files stay. Backup archive retention is set separately in the backup settings.