Each scheduler can be configured so that it is related to a database site that denotes the location of the scheduler server that processes the tasks. It is not necessary for the scheduler to monitor the various databases, because the SmartPlant Foundation servers send the task data to the centralized scheduler server.
This task information is displayed in the Desktop Client through the Find > Administration > Schedulers command, which retrieves the information from the database and displays it in the list view.
Task specific information is stored in a database for each task sent to the scheduler. This holds information necessary to process a task once, a number of times, or repeatedly on a specified schedule. The Configuration Service polls the database using a configurable interval; it will look at each of the schedulers configured in the system. If it finds an enabled scheduler, then it will see if the related site (or default site) is active. If the site is active, then it will send a request to the scheduler asking it to poll for tasks.
Each time you create a new scheduled task, the related scheduler is immediately prompted to poll for how many tasks it can process and retrieves that number to start processing. When a task is complete, the scheduler automatically polls again for more tasks. It does not wait for the default minimum polling interval of 30 minutes, which is configured to work with application pool recycling. The scheduler also polls automatically on startup and on restart of the server.
If the scheduler is already busy polling or at maximum capacity, each new task is
put in the queue and is not processed until the scheduler becomes free. Each task
tells the scheduler what service or process to run, when to run it, and where to run
it. Information about scheduled tasks is displayed in the Desktop Client through the
Query for Schedule Tasks command 
..
-
Some services may be remote (such as printing and alternate rendition) and using a remote service offloads the server. The connections may use the network or the internet. If the task fails to complete, an error message is returned to the Scheduler. These messages can be viewed in the Scheduler window.
Tasks that need to interact with the database (such as e-mail digest, data loading, and archive and purge) cannot be offloaded and are processed internally.
Some services may be remote (such as printing, title block, and alternate rendition) and using a remote service offloads the server. The connections may be via the network or the internet. If the task fails to complete, an error message is returned to the Scheduler. These messages can be viewed in the Scheduler window.
Tasks that need to interact with the database (such as e-mail digest, data loading and archive and purge) cannot be offloaded and are processed internally.