Skip to content
Task Plan Templates › Case management › Organize agent workspaces › Configure › Customer Service Management
Release: Australia · Updated: 2026-03-12 · Official documentation · View source

View task plan template executions

View tracking and diagnostic information for every execution of task plan templates in the Task Plan Template Executions table. The information available includes success, failure, and skipped details, along with references for traceability.

Before you begin

Role required: sn_task_plan.viewer

Procedure

  1. Navigate to All > Task plan templates > Published Task Plan Templates.

  2. Select a task plan template from the list, then navigate to the Task Plan Template Execution related list to see the execution record.

  3. In the record, view the information for each task plan template execution.

    The information available includes the following.

  
NumberThe task plan template execution number
Expected recordsThe total number of records expected to be created.
Created recordsHow many records actually created, once the task plan is applied.
Errored recordsHow many records were not created due to an error encountered somewhere \(for example, if there is a business rule preventing insert on the target table of the template item\)
Skipped recordsHow many records were skipped and not created, due to a condition check failing on the Template Item condition record \[sn\_task\_plan\_template\_item\_condition\]
Execution statusStatus can be `Completed`, `In_progress`, or `Completed with Errors`. If the task plan has been applied, but there are remaining template items yet to be visited/used to create records, then the status is set to `In_progress`. If the task plan has fully been applied with NO errors, then the status is set to `Completed`. If the task plan has fully been applied with NO errors, but some records were skipped, then the status is set to `Completed`. If the task plan has fully been applied with at least ONE error spotted when attempting to create a record using a template item, then the status is set to `Completed with Errors`.
Execution detailsThis is a field of type JSON. At the bare minimum, if the task plan has been applied and no records have been `"skipped"` or `"errored"`, then the JSON object looks something like this: ``` { Status: "Completed", ParentRecord: ['CS0001', 'CS0002'], RequestNumber: TPEX00001 } 
 The `Status` key in the JSON object is the same as the `execution_status` field.

 The `ParentRecord` key represents the top-level parent record\(s\) within the newly created hierarchy. It may either represent a singular Glide Record \(record existing in the database\) that was provided, or an array holding the first level of records created from ROOT template items. Root template items are template items without any parent \(top-level\).

 The `RequestNumber` key points back to the `Number` of the Task Plan Template Execution record.

 If there are skipped records or errored records, then the Template Item number of the skipped/errored item is provided. The following is an example where both 'Skipped' and 'Errored' template items were encountered during task plan execution:

 ```
{
Status: "Completed with Errors", //status is set to Completed With Errors, as we encountered an errored record
ParentRecord: ['CS0001', 'CS0002'],
RequestNumber: TPEX00001,
 Skipped: ['TP0002', 'TP0005'],
Errors: ['TP0008']
}