Scheduled Task Execution Log

The Scheduled Task Execution Log displays details of each execution of a scheduled task. The log helps you identify:

  • Executions that failed and any exceptions
  • Executions that had the longest duration
  • Whether any executions were skipped
  • The script execution details

Understanding the Scheduled Task Execution Log

As Workflow executes a scheduled task, the task moves from one state to the next in the following order:
  1. PROCESSING: Task is loading.
  2. CHECKING: Workflow is checking whether the task should be executed. When the check is complete, the log displays either OK to indicate that the task should execute, or one of the following messages that indicates why it should not be executed: 
  • ONLY_DEFAULT: The task can be executed only on the default tenant, but it is triggered on another tenant.
  • DAILY_FIRST_TIME_EXECUTION: The daily or hourly task has already been executed on this day or hour. For example, if a daily task is scheduled for 16:00 today and you ran it manually at 15:00, the task will not be executed today. Similarly, if an hourly task has already ran that hour, it will not be executed again.
  • MAX_NUMBER_OF_TIMES: The maximum number of occurrences has been reached.
  • END_DATE_PASSED: The end date of the schedule has passed.
  • IS_RUNNING: The task is already running. For example, if you started the task manually and it is still executing at the regularly scheduled time, the task will not execute again.
  1. One of the following:
  • CONDITION_NOT_PASSED: Any condition in the previous state was true. The task will not be executed and does not move to the next state. 
  • EXECUTING: The task is executing.
  1. One of the following:
  • FINISHED: The execution is complete. 
  • NOT_FINISHED: An exception occurred and the task did not execute. This state indicates a problem with the script that runs the task.  

A log entry is created for each state, with information relevant to that state. For example, the entry for the FINISHED state shows how long the task took to execute.

To open the Scheduled Task Execution Log, go to either:

  • Setup > Development > Logs > Scheduled Task Execution Log, or
  • Setup > Automation > Scheduled Tasks, then click the  button next to a scheduled task and select Show Logs.

In the log, you can:


Sort the log on a column

Click the name of the column you want.               

Filter the log on a column

In the Filter field, select the name of the column you want, then select the filter conditions and criteria.

View details of an execution

The details show whether the task is active, expired, the number of times the task was triggered, and the repeat interval.

Click the Details button.

View or edit the task schedule

 Click the name of the task.               

View or edit the Script Execution Log

Available only for executions in the EXECUTING and FINISHED states.

The Script Execution Log shows details about all processes that executed with the script. 

Click the PID of the execution you want.
View or edit the script used for the task Click the script name.

Each log entry displays the following statistics: 


Group ID

Identifies one execution of the task.

Entries for each state of an execution are grouped together under a single Group ID. For example, the first execution will create four log entries (for the CHECKING, PROCESSING, EXECUTING, and FINISHED states) with one group ID. The next  execution will create another four entries with a new Group ID.

The Process ID of the script process thread. Click the PID to see all scripts that ran with the execution.

For more information, see Script Execution Log

The name of the task.

Click the name to view or edit the execution schedule.


The name of the script that executed the task.

Click the script name to view or edit the script.

Log Date
The time of the execution, in the server time. 
The recurrence type (MONTH, WEEK, DAY, or HOUR). 

The current state of the execution.

For more information, see Understanding the Task Execution Log.


Shown only for the CHECKING state. 

Shows whether execution conditions were met.

The message OK indicates that all conditions were met. For descriptions of other messages, see the CHECKING state.
The exception, if one occurred during execution.

Shown only for the FINISHED state.  

The server that executed the task.

The amount of time the task took to execute, in milliseconds. 

Related Articles