...
Meridix Platform has a large number of settings that controls how the system behaves. The main settings are available through the Application settings page that you can access by going to Administration->Application settings in the menu.
This page is divided into several sections and each setting is described by the built in help system.
All settings are described and documented inside the system.
The execution queue is a queue with scheduled jobs that the system is going to perform. For example, every time the system executes a saved report it is added as a job to the execution queue. System administrators can view the current queue at Execution queue->View execution queue 
The page is automatically updated if the checkbox Update page automatically is checked.
Below the section on the page is described.
Studio service status Shows the current status of the Meridix Studio Server, which is the background service that executes the jobs. It should always be started otherwise none of the job will be executed.
Administrators are also presented the current status on the Quick start page.
Active Show all the jobs in the queue that are added but not yet executed. Completed Executed jobs stays in the queue with a status of Completed for a number of days. They are automatically removed by the system later. You can always re execute a completed job by clicking on the Move to active queue link. The job will be re executed in the next run.
The following information is available for both active and completed jobs.
Added to queue The timestamp when the job was added to the queue.
Last status update The timestamp for the last status update for the job. For completed jobs this is the time when the job was completed.
Status The current status of the job.
Status message A status message describing the status (if necessary).
Type of job What type of job this is (for example, Saved report).
Description A description of the job (for example, if it's a saved report job the name of the customer it belongs to and the name of the saved report).
Scheduled to execute Since jobs can be scheduled to be executed at a future date this column specify what time it is supposed to run. Saved reports can be added retrospectively and can therefore be executes as if they were executed at an earlier date. In these cases this column will contain the timestamp that the report is executed as it was.