{"id":57750,"date":"2023-07-06T09:25:38","date_gmt":"2023-07-06T08:25:38","guid":{"rendered":"https:\/\/developer.kore.ai\/v10-1\/?p=57750"},"modified":"2024-02-12T08:27:50","modified_gmt":"2024-02-12T08:27:50","slug":"task-execution-logs","status":"publish","type":"post","link":"https:\/\/developer.kore.ai\/v10-1\/docs\/bots\/analyzing-your-bot\/task-execution-logs\/","title":{"rendered":"Task Execution Logs"},"content":{"rendered":"<section class=\"l-section wpb_row height_auto\"><div class=\"l-section-h i-cf\"><div class=\"g-cols vc_row type_default valign_top\"><div class=\"vc_col-sm-12 wpb_column vc_column_container\"><div class=\"vc_column-inner\"><div class=\"wpb_wrapper\"><div class=\"w-separator size_medium\"><\/div>\r\n\t<div class=\"wpb_text_column \">\r\n\t\t<div class=\"wpb_wrapper\">\r\n\t\t\t<p>The <b>Task Execution Logs<\/b> feature helps you gain in-depth insights into the task execution-related data and assess your virtual assistant\u2019s performance in executing tasks. The <b>Analyze<\/b> &gt; <b>Task Execution Logs<\/b> page shows information specific to task execution in the following sections:<\/p>\n<ul>\n<li><b>Failed Task<\/b>: Indicates the number of unsuccessful tasks.<\/li>\n<li><b>API Calls<\/b>: Displays all the Service node and Webhook node executions-related data, and the number of failed services during Bot interactions.<\/li>\n<li><b>Script Execution<\/b>: Displays analytics data for all the script node executions and the number of failed scripts during Bot interactions.<\/li>\n<li><b>Debug Log<\/b>: Custom Debug logs include user conversations from across all channels for analyzing your VA.<\/li>\n<li><b>Pinned<\/b>: Pinned Task Execution Logs records. Specific records are pinned to highlight them for easy access and viewing.<\/li>\n<\/ul>\n<h2><span class=\"ez-toc-section\" id=\"Task_Execution_Logs_Fields\">Task Execution Logs Fields<\/span><\/h2>\n<p><span style=\"font-weight: 400;\">The <\/span><b>Analyze<\/b><span style=\"font-weight: 400;\"> &gt; <\/span><b>Task Execution Logs<\/b><span style=\"font-weight: 400;\"> page displays the following fields specific to task execution:<\/span><\/p>\n<h3><span class=\"ez-toc-section\" id=\"Failed_Task\"><span style=\"font-weight: 400;\">Failed Task<\/span><\/span><\/h3>\n<p><span style=\"font-weight: 400;\">In a scenario where all the user utterances are successfully mapped to an intent, but the task cannot be completed for some reason, then such utterances are listed under this tab. You can group them based on task and failure types to analyze and solve issues with the VA.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">See the following table<\/span><span style=\"font-weight: 400;\">\u00a0and the <a href=\"https:\/\/developer.kore.ai\/v10-1\/docs\/bots\/analyzing-your-bot\/task-execution-logs\/#Features\" rel=\"noopener noreferrer\">Features<\/a> section to know more:<\/span><\/p>\n<p><a ref=\"magnificPopup\" href=\"https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v10-1\/wp-content\/uploads\/sites\/35\/20230703110331\/Task-Execution-logs-1-1.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-57693\" src=\"https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v10-1\/wp-content\/uploads\/sites\/35\/20230703110331\/Task-Execution-logs-1-1.png\" alt=\"\" width=\"600\" height=\"350\" \/><\/a><\/p>\n<h3><span class=\"ez-toc-section\" id=\"Failed_Task_Type_of_Issues\"><span style=\"font-weight: 400;\">Failed Task &#8211; Type of Issues<\/span><\/span><\/h3>\n<p><span style=\"font-weight: 400;\">Different types of issues that occur during a <\/span> <a href=\"https:\/\/developer.kore.ai\/v10-1\/docs\/bots\/analyzing-your-bot\/task-execution-logs\/#Failed_Task\" rel=\"noopener noreferrer\">Failed Task<\/a> <span style=\"font-weight: 400;\"> are listed as follows:<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">Task aborted by user<\/span><\/li>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">Alternate task initiated<\/span><\/li>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">Chat Interface refreshed<\/span><\/li>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">Human agent transfer<\/span><\/li>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">Authorization attempt failure \u2013 Max attempts reached<\/span><\/li>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">Incorrect entity failure \u2013 Max attempts reached<\/span><\/li>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">Script failure<\/span><\/li>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">Service failure<\/span><\/li>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">Inactivity or External Events (from ver8.0) \u2013 when the conversation session and as a result, the in-progress task is closed due to inactivity or external events.<\/span><\/li>\n<\/ul>\n<p><strong>Description of Failed Task Fields<\/strong><\/p>\n<p><span style=\"font-weight: 400;\">The following table lists the fields on the Failed Task tab with descriptions:<\/span><\/p>\n<table>\n<thead>\n<tr>\n<th><b>Fields<\/b><\/th>\n<th><b>Description<\/b><\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><span style=\"font-weight: 400;\">Utterances<\/span><\/td>\n<td><span style=\"font-weight: 400;\">The utterances that are successfully mapped to an intent, but still the task failed due to some issue. The details in the tab are grouped by utterances based on similarity by default. To turn off grouping by utterance, click the <\/span><b>Utterances <\/b><span style=\"font-weight: 400;\">header and turn off the <\/span><b>Group by Utterances<\/b><span style=\"font-weight: 400;\"> option.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Task Name<\/span><\/td>\n<td><span style=\"font-weight: 400;\">The task that is identified for the user utterance. To turn on grouping by task name, click the <\/span><b>Task Name <\/b><span style=\"font-weight: 400;\">header and enable the <\/span><b>Group by Task <\/b><span style=\"font-weight: 400;\">option.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Failure Point<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Nodes or points in the task execution journey where the failure occurred, resulting in the task cancellation or user drop. Click an entry to view the complete conversation for that session with markers to identify the intent detection utterance and the failure\/drop-out point. Depending on the task type, clicking Failure Point shows more details.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Type of Issue<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Shows the reason for failure in case of Task Failure records.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">UserID<\/span><\/td>\n<td><span style=\"font-weight: 400;\">The UserID of the end user related to the conversation. You can view the metrics based on either <\/span><b>Kore User id<\/b><span style=\"font-weight: 400;\"> or <\/span><b>Channel User Id<\/b><span style=\"font-weight: 400;\">.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Channel-specific ids are shown only for the users who have interacted with the VA during the selected period.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Language<\/span><\/td>\n<td><span style=\"font-weight: 400;\">The language in which the conversation occurred.<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><span style=\"font-weight: 400;\">If it is a multi-lingual VA, you can select specific languages to filter the conversation that occurred in those languages. The page shows the conversations that occurred in all enabled languages by default.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Date &amp; Time<\/span><\/td>\n<td><span style=\"font-weight: 400;\">The date and time of the chat. You can sort the data by either <\/span><b>Newest to Oldest<\/b><span style=\"font-weight: 400;\">\u00a0or <\/span><b>Oldest to Newest<\/b><span style=\"font-weight: 400;\">.<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h3><span class=\"ez-toc-section\" id=\"Performance\"><span style=\"font-weight: 400;\">Performance<\/span><\/span><\/h3>\n<p>Developers can monitor all the scripts and API services across the VA\u2019s tasks from a single window. The performance tab displays information<span style=\"font-weight: 400;\"> related to the backend performance of the VA in two sections, namely <b>API Calls<\/b> and <b>Script Execution<\/b>. <\/span><span style=\"font-weight: 400;\">The platform stores the following meta-information:<\/span><\/p>\n<h3><span class=\"ez-toc-section\" id=\"API_Calls\">API Calls<\/span><\/h3>\n<p>The <strong>API Calls<\/strong> <span style=\"font-weight: 400;\">section provides information on the API calls execution performance for a Service Node or Webhook based on the following metrics:<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Node name, Type, and task name.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Success %<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Channel<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">The total number of calls with a 200 (success) responses and the total number of calls with a non-200 (failure) response. You can view the actual response code from the details page that opens when you click the service row.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Average Response times<\/span><\/li>\n<\/ul>\n<p><strong>Description of the API Calls Fields<\/strong><\/p>\n<p><span style=\"font-weight: 400;\">The following table lists the fields in the API Calls section with their descriptions:<\/span><\/p>\n<table>\n<thead>\n<tr>\n<th><b>Fields<\/b><\/th>\n<th><b>Description<\/b><\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><span style=\"font-weight: 400;\">Node Name<\/span><\/td>\n<td><span style=\"font-weight: 400;\">The name of the service or script or Webhook within the task that got executed in response to the user utterance. The <\/span><b>Node Name<\/b><span style=\"font-weight: 400;\"> column displays the names of the Preprocessor script node, API call, and the Postprocessor script node.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">To turn on grouping by components to which the Webhook services belong, click the <\/span><b>Node Name <\/b><span style=\"font-weight: 400;\">header and turn on the <\/span><b>Group by NodeName <\/b><span style=\"font-weight: 400;\">option.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">To turn on grouping by Pre and Postprocessor scripts for a Service Node, click the <\/span><b>Node Name <\/b><span style=\"font-weight: 400;\">header and enable the <\/span><b>Group by NodeName <\/b>(<b>PreProcessor or PostProcessor Script<\/b>)<span style=\"font-weight: 400;\"> option.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Type<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Shows whether it is a script or service or Webhook.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Webhook details are included from ver 7.0.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Task Name<\/span><\/td>\n<td><span style=\"font-weight: 400;\">The task that is identified for the user utterance. To turn on grouping by task name, click the <\/span><b>Task Name <\/b><span style=\"font-weight: 400;\">header and enable the <\/span><b>Group by Task <\/b><span style=\"font-weight: 400;\">option.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Success%<\/span><\/td>\n<td><span style=\"font-weight: 400;\">The percentage of successful service or script node task executions.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Channel<\/span><\/td>\n<td><span style=\"font-weight: 400;\">The channel on which the Service\/Webhook task execution is performed<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">2XX Responses<\/span><\/td>\n<td><span style=\"font-weight: 400;\">The percentage of the service or script runs that returned a 2xx API response.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Non 2XX Responses<\/span><\/td>\n<td><span style=\"font-weight: 400;\">The percentage of the service or script runs that returned a non-2xx API response.<\/span><\/td>\n<\/tr>\n<tr>\n<td>Avg Response Time<\/td>\n<td>The average response time of the script or service in the total number of runs.<\/p>\n<p>For a Service node, this value displays the<strong> total execution time<\/strong> for the <strong>Preprocessor script<\/strong>, <strong>API<\/strong>, and <strong>Postprocessor script<\/strong> calls.<\/p>\n<p><b>Note<\/b>: The execution times for each of these calls is maintained separately in the backend.<\/p>\n<p><span style=\"font-weight: 400;\">This can be sorted from <\/span><b>High to Low<\/b><span style=\"font-weight: 400;\"> or<\/span><b> Low to High<\/b><span style=\"font-weight: 400;\"> under the <\/span><b>Performance <\/b><span style=\"font-weight: 400;\">tab.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Status Code<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Filter service executions based on the status codes. From the <\/span><b>More Filters <\/b><span style=\"font-weight: 400;\">drop-down menu &gt; <\/span><b>Status Code<\/b><span style=\"font-weight: 400;\">, you can choose one or more status codes:<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Success status code: 200\u00a0<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Non-success status code: 304, 400, 401, 403, 404, 408, 409, 500, 502, 503, and 504<\/span><\/li>\n<\/ul>\n<p><a ref=\"magnificPopup\" href=\"https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v10-1\/wp-content\/uploads\/sites\/35\/20231016072425\/status_codes.png\"><img loading=\"lazy\" decoding=\"async\" width=\"1917\" height=\"681\" class=\"alignnone size-medium wp-image-59801\" src=\"https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v10-1\/wp-content\/uploads\/sites\/35\/20231016072425\/status_codes.png\" alt=\"\" srcset=\"https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v10-1\/wp-content\/uploads\/sites\/35\/20231016072425\/status_codes.png 1917w, https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v10-1\/wp-content\/uploads\/sites\/35\/20231016072425\/status_codes-300x107.png 300w, https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v10-1\/wp-content\/uploads\/sites\/35\/20231016072425\/status_codes-1024x364.png 1024w\" sizes=\"auto, (max-width: 1917px) 100vw, 1917px\" \/><\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h3><span class=\"ez-toc-section\" id=\"Script_Execution\">Script Execution<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">The <\/span><b>Script Execution<\/b><span style=\"font-weight: 400;\"> section provides information on the VA\u2019s script execution performance based on the following metrics:<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Node name and task name<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Success %<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Channel<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Average Response Times<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Appropriate alerts if a script or a service is failing consecutively.<\/span><\/li>\n<\/ul>\n<p><strong>Description of the Script Execution Fields<\/strong><\/p>\n<p><span style=\"font-weight: 400;\">The following table lists the fields in the Script Execution section with their descriptions:<\/span><\/p>\n<p>&nbsp;<\/p>\n<table>\n<thead>\n<tr>\n<th><b>Fields<\/b><\/th>\n<th><b>Description<\/b><\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><span style=\"font-weight: 400;\">Node Name<\/span><\/td>\n<td><span style=\"font-weight: 400;\">The name of the service or script or Webhook within the task that was executed in response to the user utterance. The Node Name displays the names of the Preprocessor, Service, and Postprocessor script nodes.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">To turn on grouping by components to which the Webhook services belong, click the <\/span><b>Node Name <\/b><span style=\"font-weight: 400;\">header and turn on the <\/span><b>Group by NodeName <\/b><span style=\"font-weight: 400;\">option.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">To turn on grouping by Pre and Postprocessor scripts for a Service Node, click the <\/span><b>Node Name <\/b><span style=\"font-weight: 400;\">header and enable the <\/span><b>Group by NodeName<\/b> (<b>PreProcessor Script or PostProcessor Script<\/b>)<span style=\"font-weight: 400;\"> option.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Task Name<\/span><\/td>\n<td><span style=\"font-weight: 400;\">The task that is identified for the user utterance. To turn on grouping by task name, click the <\/span><b>Task Name <\/b><span style=\"font-weight: 400;\">header and enable the <\/span><b>Group by Task <\/b><span style=\"font-weight: 400;\">option.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Success%<\/span><\/td>\n<td><span style=\"font-weight: 400;\">The percentage of the service or script runs that got executed successfully.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Channel<\/span><\/td>\n<td><span style=\"font-weight: 400;\">The channel on which the Script task execution is performed.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Avg Response Time<\/span><\/td>\n<td>The average response time of the script or service in the total number of runs.<\/p>\n<p>For a Service node, this value displays the <strong>Total Execution Time<\/strong> for the <strong>Preprocessor<\/strong>, <strong>Service Node<\/strong>, and <strong>Postprocessor<\/strong> script calls. Please refer to the image below.<\/p>\n<p><b>Note<\/b>: The execution times for each of these calls is maintained separately in the backend.<\/p>\n<p>This can be sorted from High to Low or Low to High under the <strong>Performance<\/strong> tab.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><a ref=\"magnificPopup\" href=\"https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v10-1\/wp-content\/uploads\/sites\/35\/20240210062912\/task-execution-logs.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-61109\" src=\"https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v10-1\/wp-content\/uploads\/sites\/35\/20240210062912\/task-execution-logs.png\" alt=\"\" width=\"600\" height=\"450\" \/><\/a><\/p>\n<h3><span class=\"ez-toc-section\" id=\"Script_Performance\">Script Performance<\/span><\/h3>\n<p>On the <strong>Performance Dashboard<\/strong>, the service node\u2019s script execution details are displayed in the <strong>Script Execution Rate<\/strong> section. <a href=\"https:\/\/developer.kore.ai\/v10-1\/docs\/bots\/analyzing-your-bot\/performance-dashboard\/#Script_Execution_Rate\" target=\"_blank\" rel=\"noopener noreferrer\">\u00a0Learn more<\/a>.<\/p>\n<p>Additionally, the <strong>Script Performance<\/strong> section displays information on the Service Node execution. <a href=\"https:\/\/developer.kore.ai\/v10-1\/docs\/bots\/analyzing-your-bot\/performance-dashboard\/#Script_Performance\" target=\"_blank\" rel=\"noopener noreferrer\">Learn more<\/a>.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Debug_Log\"><span style=\"font-weight: 400;\">Debug Log<\/span><\/span><\/h3>\n<p><span style=\"font-weight: 400;\">Any custom debug statements that you entered in the Script node using the script <\/span><span style=\"font-weight: 400;\"><code>koreDebugger.log(\"&lt;debug statement&gt;\")<\/code><\/span><span style=\"font-weight: 400;\">are displayed on this tab. Debug statements should be in a string format. See the following table <\/span><span style=\"font-weight: 400;\">to know more:<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The logs include the user conversation from across all channels. You can use them for bot analysis, especially in case of failures during user interaction.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The details include the following:<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">The actual statement that you have defined at the time of Bot definition.<\/span><\/li>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">Date and time of logging<\/span><\/li>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">Channel<\/span><\/li>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">User ID (along with channel-specific id)<\/span><\/li>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">Language of interaction<\/span><\/li>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">Task name, if available<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">You can also view the details of the chat history associated with the session. To view more details, follow the below steps:<\/span><\/p>\n<ol>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">Click a logged record.<\/span><\/li>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">On the corresponding window, you can find the <\/span><b>Details<\/b><span style=\"font-weight: 400;\"> and <\/span><b>Chat History<\/b><span style=\"font-weight: 400;\"> tabs.<\/span><\/li>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">Under the Details tab, you can find the <\/span><i><span style=\"font-weight: 400;\">task name<\/span><\/i><span style=\"font-weight: 400;\">, <\/span><i><span style=\"font-weight: 400;\">channel<\/span><\/i><span style=\"font-weight: 400;\">, <\/span><i><span style=\"font-weight: 400;\">language<\/span><\/i><span style=\"font-weight: 400;\">, and <\/span><i><span style=\"font-weight: 400;\">flow<\/span><\/i><span style=\"font-weight: 400;\">.<\/span><\/li>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">Click the <\/span><b>Chat History<\/b><span style=\"font-weight: 400;\"> tab. You can find the chat transcript where the log is recorded.<\/span>\n<ul>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">If the debug log is generated from a VA message, you are navigated to that specific message in the chat transcript.<\/span><\/li>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">If the debug log is not part of the VA message, you are navigated to the latest message added before the debug statement.<\/span><\/li>\n<\/ul>\n<\/li>\n<\/ol>\n<p><span style=\"font-weight: 400;\">For universal VAs, the debug statements from the universal and linked assistants are included in the logs. The debug logs also include the error messages related to BotKit, for example, when the platform could not reach the BotKit or when the BotKit did not acknowledge the message sent by the platform. The message includes details like the<\/span> <code><i><span style=\"font-weight: 400;\">&lt;endpoint&gt;<\/span><\/i><span style=\"font-weight: 400;\">, <\/span><i><span style=\"font-weight: 400;\">&lt;error code&gt;<\/span><\/i><span style=\"font-weight: 400;\">,<\/span><\/code> and <code><i><span style=\"font-weight: 400;\">&lt;response time&gt;<\/span><\/i><i><span style=\"font-weight: 400;\">.<\/span><\/i><\/code><\/p>\n<p><strong>Description of Debug Log Fields<\/strong><\/p>\n<p><span style=\"font-weight: 400;\">The following table lists the fields on the Debug Log tab with descriptions:<\/span><\/p>\n<table>\n<thead>\n<tr>\n<th><b>Fields<\/b><\/th>\n<th><b>Description<\/b><\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><span style=\"font-weight: 400;\">Log<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Description of the debug log. For example, <\/span><span style=\"font-weight: 400;\">getIndex is not defined.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Task Name<\/span><\/td>\n<td><span style=\"font-weight: 400;\">The task that is identified for the user utterance. To turn on grouping by task name, click the <\/span><b>Task Name <\/b><span style=\"font-weight: 400;\">header and enable the <\/span><b>Group by Task <\/b><span style=\"font-weight: 400;\">option.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Debug Point\u00a0<\/span><\/td>\n<td><span style=\"font-weight: 400;\">The point or a node in the conversation where the error is identified. <\/span><span style=\"font-weight: 400;\">For example, <\/span><span style=\"font-weight: 400;\">buildDataForCarousel<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Channel<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Specific channel where the conversation occurred.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Language<\/span><\/td>\n<td><span style=\"font-weight: 400;\">The language in which the conversation occurred.<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><span style=\"font-weight: 400;\">If it is a multi-lingual VA, you can select specific languages to filter the conversation that occurred in those languages. The page shows the conversations that occurred in all enabled languages by default.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">UserID<\/span><\/td>\n<td><span style=\"font-weight: 400;\">The UserID of the end user related to the conversation. You can view the metrics based on either <\/span><b>Kore User id<\/b><span style=\"font-weight: 400;\"> or <\/span><b>Channel User Id<\/b><span style=\"font-weight: 400;\">.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Channel-specific ids are shown only for the users who have interacted with the VA during the selected period.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Date &amp; Time<\/span><\/td>\n<td><span style=\"font-weight: 400;\">The date and time of the chat. You can sort the data by either <\/span><b>Newest to Oldest<\/b><span style=\"font-weight: 400;\">\u00a0or <\/span><b>Oldest to Newest<\/b><span style=\"font-weight: 400;\">.<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h3><span class=\"ez-toc-section\" id=\"Pinned\"><span style=\"font-weight: 400;\">Pinned<\/span><\/span><\/h3>\n<p>Any records from the <b>Failed Tasks<\/b>, <b>API Calls<\/b>, and <b>Script Execution<\/b> sections that are pinned are displayed here. The fields available in the Pinned section under <b>Task Execution Logs<\/b> are listed here as well. However, they pertain to Task Execution Logs. <a href=\"https:\/\/developer.kore.ai\/v10-1\/docs\/bots\/analyzing-your-bot\/bot-analysis\/#Pinned\" target=\"_blank\" rel=\"noopener noreferrer\">Learn more<\/a>.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Storage_Limitations\"><span style=\"font-weight: 400;\">Storage Limitations<\/span><\/span><\/h3>\n<p><span style=\"font-weight: 400;\">The platform imposes restrictions on the number of log statements retained per VA. The limit is a combination of volume and period:<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">Only the latest 700 statements per VA are stored.<\/span><\/li>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">Statements older than 7 days are removed.<\/span><\/li>\n<\/ul>\n<h1><span class=\"ez-toc-section\" id=\"Task_Execution_Logs_Analysis\">Task Execution Logs Analysis<\/span><\/h1>\n<p>The following sections describe more about the options available on Task Execution Logs page and the analysis of the records captured here.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Features\"><span style=\"font-weight: 400;\">Features<\/span><\/span><\/h2>\n<p><span style=\"font-weight: 400;\">The following list details the features available for Task Execution Logs including Failed Tasks, API Calls, Script Execution, and Debug Log.<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">You can filter the information based on various criteria such as User Utterances, Intent, user id (Kore user id or channel-specific unique id), date-period, the channel of use, language, etc. You can also filter records based on multiple custom tags. See <\/span><a href=\"https:\/\/developer.kore.ai\/v10-1\/docs\/bots\/analyzing-your-bot\/bot-analysis\/#Filter_Criteria\"><span style=\"font-weight: 400;\">Filter Criteria<\/span><\/a><span style=\"font-weight: 400;\"> to know more.<\/span><\/li>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">Complete meta information is stored for later analysis, including the original user utterance, the channel of communication, entities extracted (if any), custom tags applied, detailed Task Execution Logs.<\/span><\/li>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">Any important record you want to mark, track later, or both can be pinned which appear on\u00a0the <\/span><b>Pinned<\/b><span style=\"font-weight: 400;\"> tab.<\/span><\/li>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">Sorting feature is available for Date and Time (Oldest to Newest, Newest to Oldest). You can export the insights data as a CSV file.<\/span><\/li>\n<\/ul>\n<h2><span class=\"ez-toc-section\" id=\"Fields_Matrix\"><span style=\"font-weight: 400;\">Fields Matrix<\/span><\/span><\/h2>\n<p><span style=\"font-weight: 400;\">The following matrix shows the availability of fields on each tab of the Task Execution Log dashboard:<\/span><\/p>\n<table>\n<thead>\n<tr>\n<th><b>Field<\/b><\/th>\n<th><b>Failed Tasks<\/b><\/th>\n<th><b>API Calls<\/b><\/th>\n<th><b>Script Execution<\/b><\/th>\n<th><b>Pinned<\/b><\/th>\n<th><b>Debug Log<\/b><\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><span style=\"font-weight: 400;\">Utterances<\/span><\/td>\n<td><span style=\"font-weight: 400;\">\u2714<\/span><\/td>\n<td><span style=\"font-weight: 400;\">X<\/span><\/td>\n<td><span style=\"font-weight: 400;\">X<\/span><\/td>\n<td><span style=\"font-weight: 400;\">\u2714<\/span><\/td>\n<td><span style=\"font-weight: 400;\">X<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Intent<\/span><\/td>\n<td><span style=\"font-weight: 400;\">X<\/span><\/td>\n<td><span style=\"font-weight: 400;\">X<\/span><\/td>\n<td><span style=\"font-weight: 400;\">X<\/span><\/td>\n<td><span style=\"font-weight: 400;\">\u2714<\/span><\/td>\n<td><span style=\"font-weight: 400;\">X<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Traits<\/span><\/td>\n<td><span style=\"font-weight: 400;\">X<\/span><\/td>\n<td><span style=\"font-weight: 400;\">X<\/span><\/td>\n<td><span style=\"font-weight: 400;\">X<\/span><\/td>\n<td><span style=\"font-weight: 400;\">X<\/span><\/td>\n<td><span style=\"font-weight: 400;\">X<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">UserID<\/span><\/td>\n<td><span style=\"font-weight: 400;\">\u2714<\/span><\/td>\n<td><span style=\"font-weight: 400;\">X<\/span><\/td>\n<td><span style=\"font-weight: 400;\">X<\/span><\/td>\n<td><span style=\"font-weight: 400;\">\u2714<\/span><\/td>\n<td><span style=\"font-weight: 400;\">\u2714<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Language<\/span><\/td>\n<td><span style=\"font-weight: 400;\">\u2714<\/span><\/td>\n<td><span style=\"font-weight: 400;\">X<\/span><\/td>\n<td><span style=\"font-weight: 400;\">X<\/span><\/td>\n<td><span style=\"font-weight: 400;\">\u2714<\/span><\/td>\n<td><span style=\"font-weight: 400;\">\u2714<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Date &amp; Time<\/span><\/td>\n<td><span style=\"font-weight: 400;\">\u2714<\/span><\/td>\n<td><span style=\"font-weight: 400;\">X<\/span><\/td>\n<td><span style=\"font-weight: 400;\">X<\/span><\/td>\n<td><span style=\"font-weight: 400;\">\u2714<\/span><\/td>\n<td><span style=\"font-weight: 400;\">\u2714<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Prompt Type<\/span><\/td>\n<td><span style=\"font-weight: 400;\">X<\/span><\/td>\n<td><span style=\"font-weight: 400;\">X<\/span><\/td>\n<td><span style=\"font-weight: 400;\">X<\/span><\/td>\n<td><span style=\"font-weight: 400;\">X<\/span><\/td>\n<td><span style=\"font-weight: 400;\">X<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Task Name<\/span><\/td>\n<td><span style=\"font-weight: 400;\">\u2714<\/span><\/td>\n<td><span style=\"font-weight: 400;\">\u2714<\/span><\/td>\n<td><span style=\"font-weight: 400;\">\u2714<\/span><\/td>\n<td><span style=\"font-weight: 400;\">X<\/span><\/td>\n<td><span style=\"font-weight: 400;\">\u2714<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Node Name<\/span><\/td>\n<td><span style=\"font-weight: 400;\">X<\/span><\/td>\n<td><span style=\"font-weight: 400;\">\u2714<\/span><\/td>\n<td><span style=\"font-weight: 400;\">\u2714<\/span><\/td>\n<td><span style=\"font-weight: 400;\">X<\/span><\/td>\n<td><span style=\"font-weight: 400;\">X<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Failure Point<\/span><\/td>\n<td><span style=\"font-weight: 400;\">\u2714<\/span><\/td>\n<td><span style=\"font-weight: 400;\">X<\/span><\/td>\n<td><span style=\"font-weight: 400;\">X<\/span><\/td>\n<td><span style=\"font-weight: 400;\">X<\/span><\/td>\n<td><span style=\"font-weight: 400;\">X<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Type of Issue<\/span><\/td>\n<td><span style=\"font-weight: 400;\">\u2714<\/span><\/td>\n<td><span style=\"font-weight: 400;\">X<\/span><\/td>\n<td><span style=\"font-weight: 400;\">X<\/span><\/td>\n<td><span style=\"font-weight: 400;\">\u2714<\/span><\/td>\n<td><span style=\"font-weight: 400;\">X<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Type<\/span><\/td>\n<td><span style=\"font-weight: 400;\">X<\/span><\/td>\n<td><span style=\"font-weight: 400;\">\u2714<\/span><\/td>\n<td><span style=\"font-weight: 400;\">\u2714<\/span><\/td>\n<td><span style=\"font-weight: 400;\">X<\/span><\/td>\n<td><span style=\"font-weight: 400;\">X<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Total Runs<\/span><\/td>\n<td><span style=\"font-weight: 400;\">X<\/span><\/td>\n<td><span style=\"font-weight: 400;\">\u2714<\/span><\/td>\n<td><span style=\"font-weight: 400;\">\u2714<\/span><\/td>\n<td><span style=\"font-weight: 400;\">X<\/span><\/td>\n<td><span style=\"font-weight: 400;\">X<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Success%<\/span><\/td>\n<td><span style=\"font-weight: 400;\">X<\/span><\/td>\n<td><span style=\"font-weight: 400;\">\u2714<\/span><\/td>\n<td><span style=\"font-weight: 400;\">\u2714<\/span><\/td>\n<td><span style=\"font-weight: 400;\">X<\/span><\/td>\n<td><span style=\"font-weight: 400;\">X<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">2XX Responses<\/span><\/td>\n<td><span style=\"font-weight: 400;\">X<\/span><\/td>\n<td><span style=\"font-weight: 400;\">\u2714<\/span><\/td>\n<td><span style=\"font-weight: 400;\">\u2714<\/span><\/td>\n<td><span style=\"font-weight: 400;\">X<\/span><\/td>\n<td><span style=\"font-weight: 400;\">X<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Non 2XX Responses<\/span><\/td>\n<td><span style=\"font-weight: 400;\">X<\/span><\/td>\n<td><span style=\"font-weight: 400;\">\u2714<\/span><\/td>\n<td><span style=\"font-weight: 400;\">\u2714<\/span><\/td>\n<td><span style=\"font-weight: 400;\">X<\/span><\/td>\n<td><span style=\"font-weight: 400;\">X<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Avg Response Time<\/span><\/td>\n<td><span style=\"font-weight: 400;\">X<\/span><\/td>\n<td><span style=\"font-weight: 400;\">\u2714<\/span><\/td>\n<td><span style=\"font-weight: 400;\">\u2714<\/span><\/td>\n<td><span style=\"font-weight: 400;\">X<\/span><\/td>\n<td><span style=\"font-weight: 400;\">X<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Log<\/span><\/td>\n<td><span style=\"font-weight: 400;\">X<\/span><\/td>\n<td><span style=\"font-weight: 400;\">X<\/span><\/td>\n<td><span style=\"font-weight: 400;\">X<\/span><\/td>\n<td><span style=\"font-weight: 400;\">X<\/span><\/td>\n<td><span style=\"font-weight: 400;\">\u2714<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Debug Point<\/span><\/td>\n<td><span style=\"font-weight: 400;\">X<\/span><\/td>\n<td><span style=\"font-weight: 400;\">X<\/span><\/td>\n<td><span style=\"font-weight: 400;\">X<\/span><\/td>\n<td><span style=\"font-weight: 400;\">X<\/span><\/td>\n<td><span style=\"font-weight: 400;\">\u2714<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Channel<\/span><\/td>\n<td><span style=\"font-weight: 400;\">X<\/span><\/td>\n<td><span style=\"font-weight: 400;\">X<\/span><\/td>\n<td><span style=\"font-weight: 400;\">X<\/span><\/td>\n<td><span style=\"font-weight: 400;\">X<\/span><\/td>\n<td><span style=\"font-weight: 400;\">\u2714<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n\r\n\t\t<\/div>\r\n\t<\/div>\r\n<div class=\"w-separator size_medium\"><\/div><\/div><\/div><\/div><\/div><\/div><\/section>\n","protected":false},"excerpt":{"rendered":"The Task Execution Logs feature helps you gain in-depth insights into the task execution-related data and assess your virtual assistant\u2019s performance in executing tasks. The Analyze &gt; Task Execution Logs page shows information specific to task execution in the following sections: Failed Task: Indicates the number of unsuccessful tasks. API Calls: Displays all the Service...","protected":false},"author":21,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[45],"tags":[],"class_list":["post-57750","post","type-post","status-publish","format-standard","hentry","category-analyzing-your-bot"],"_links":{"self":[{"href":"https:\/\/developer.kore.ai\/v10-1\/wp-json\/wp\/v2\/posts\/57750","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/developer.kore.ai\/v10-1\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/developer.kore.ai\/v10-1\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/developer.kore.ai\/v10-1\/wp-json\/wp\/v2\/users\/21"}],"replies":[{"embeddable":true,"href":"https:\/\/developer.kore.ai\/v10-1\/wp-json\/wp\/v2\/comments?post=57750"}],"version-history":[{"count":18,"href":"https:\/\/developer.kore.ai\/v10-1\/wp-json\/wp\/v2\/posts\/57750\/revisions"}],"predecessor-version":[{"id":61144,"href":"https:\/\/developer.kore.ai\/v10-1\/wp-json\/wp\/v2\/posts\/57750\/revisions\/61144"}],"wp:attachment":[{"href":"https:\/\/developer.kore.ai\/v10-1\/wp-json\/wp\/v2\/media?parent=57750"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/developer.kore.ai\/v10-1\/wp-json\/wp\/v2\/categories?post=57750"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/developer.kore.ai\/v10-1\/wp-json\/wp\/v2\/tags?post=57750"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}