Skip to content
Scope4mation · Service Automation Suite
SASService Automation Suite
SAS Wiki
AvailablePublic

Scheduler / Taakplanner

Start recurring work at the agreed time.

SIMPLY EXPLAINED

What can you do with it?

A task must run every day. Choose the action, set the schedule and check the execution.

  1. Scheduled time
  2. Scheduler
  3. Execution

How to start

  1. Choose the action
  2. Set the schedule
  3. Review runs and errors
Continue with the guide →
On this page

One-off and daily

Start actions once or at a fixed time each day.

Recurring patterns

Run tasks on a recurring pattern or a cron-like schedule.

Multiple actions

Combine actions in one job and define their execution order.

Pre- and post-actions

Run preparatory or finishing actions around a job.

Manual execution

Start a scheduled task manually when operational control requires it.

Errors and retention

Use error handling, history and retention for operations and analysis.

Where customers use Scheduler

Scheduler is used for operational automation around TOPdesk, dataflows, periodic checks and other actions that need to run at a set time or interval.

  • Periodic TOPdesk actions or synchronisations.
  • Scheduled Dataflow execution.
  • Verification and cleanup tasks.
  • Actions that must run in a fixed order.

Where to look when something goes wrong

Check the schedule, last run, action order, logging and error handling. Wiki 3.0 connects Scheduler documentation with TOPdesk, Automation, Dataflow and troubleshooting.

Troubleshooting · TOPdesk · Dataflow

Scheduler and Process Orchestrator

Scheduler: current operation

Schedules and starts tasks and actions. This existing execution layer remains documented while customers use it.

Process Orchestrator: in development

The intended future control layer for processes, exceptions, status, collaboration and governance. Operational instructions are published when functionality is available.

Read the current product direction →

Part of the transition from Qixium to SAS

The datacentre and CMP migration does not remove Scheduler from the documentation. The new environment keeps existing operations recognisable while new SAS capabilities are added gradually.

·

Take the next step

Use the reference material for details or discuss your question with the team.

Ask your question