Use this file to discover all available pages before exploring further.
Back to Analytics OverviewTask Execution Logs provides in-depth insights into task execution data to help you assess your AI Agent’s performance in executing tasks.To view the Task Execution Logs dashboard:
Click Analytics on the left navigation pane. The Analytics panel opens with the list of reports.
Click Task Execution Logs under the Automation section of the Analytics panel.
Select appropriate filters and click Apply.
The Task Execution Logs page shows information in the following sections:
Failed Task: Indicates the number of unsuccessful tasks.
API Calls: Displays Service node and Webhook node execution data and the number of failed services during AI Agent interactions.
Script Execution: Displays analytics data for script node executions and the number of failed scripts during AI Agent interactions.
Debug Log: Custom debug logs including user conversations from all channels for analyzing your AI Agent.
Pinned: Pinned Task Execution Log records for easy access and viewing.
When user utterances are successfully mapped to an intent but the task cannot be completed, those utterances appear under this tab. Group them by task and failure type to analyze and resolve issues.
The following types of issues can occur during a failed task:
Task aborted by user
Alternate task initiated
Chat interface refreshed
Human-agent transfer
Authorization attempt failure — Max attempts reached
Incorrect entity failure — Max attempts reached
Script failure
Service failure
Inactivity or External Events (from version 8.0) — when the conversation session and in-progress task is closed due to inactivity or external events
Field
Description
Utterances
Utterances mapped to an intent but where the task failed. Grouped by similarity by default. Click the Utterances header to disable Group by Utterances.
Task Name
The task identified for the user utterance. Click the Task Name header to enable Group by Task.
Failure Point
Nodes or points in the task execution journey where the failure occurred. Click an entry to view the complete conversation with markers for intent detection and failure/drop-out points.
Type of Issue
The reason for failure in the case of Task Failure records.
UserID
The end user’s ID. View metrics by Kore User ID or Channel User ID. Channel-specific IDs are shown only for users who interacted during the selected period.
Language
The language in which the conversation occurred. Defaults to all enabled languages.
Date & Time
Date and time of the chat. Sort by Newest to Oldest or Oldest to Newest.
Developers can monitor all scripts and API services across the AI Agent’s tasks from a single window. The Performance tab displays information in two sections: API Calls and Script Execution.
The API Calls section provides information on API execution performance based on the following metrics:
Node name, type, and task name
Success %
Total number of calls with 200 responses and with non-200 responses (view the actual response code from the details page opened by clicking the service row)
Average response times
Field
Description
Node Name
The name of the service, script, or Webhook within the task. Click the Node Name header to enable Group by NodeName.
Type
Indicates whether it is a script, service, or Webhook. Webhook details are included from version 7.0.
Task Name
The task identified for the user utterance. Click the Task Name header to enable Group by Task.
Success%
The percentage of service or script runs that executed successfully.
2XX Responses
The percentage of service or script runs that returned a 2xx response.
Non 2XX Responses
The percentage of service or script runs that returned a non-2xx response.
Avg Response Time
The average response time of the script or service. Sortable from High to Low or Low to High under the Performance tab.
Status Code
Filter service executions by status code via More Filters > Status Code. Success code: 200. Non-success codes: 304, 400, 401, 403, 404, 408, 409, 500, 502, 503, and 504.
Custom debug statements entered in the Script node using koreDebugger.log("debug statement") are displayed on this tab. Debug statements must be in string format. Logs include user conversations from all channels and are useful for AI Agent analysis, especially in case of failures.The details include:
The actual statement defined during AI Agent definition
Date and time of logging
Channel
User ID (along with channel-specific ID)
Language of interaction
Task name, if available
To view chat history details associated with a debug session:
Click a logged record.
The corresponding window shows Details and Chat History tabs.
Under Details, find the task name, channel, language, and flow.
Click the Chat History tab to find the chat transcript where the log is recorded.
If the debug log is generated from an AI Agent message, you are navigated to that specific message in the transcript.
If the debug log is not part of the AI Agent message, you are navigated to the latest message added before the debug statement.
For universal AI Agents, debug statements from the universal and linked AI Agents are included in the logs. Debug logs also include error messages related to BotKit, such as when the platform could not reach the BotKit or when the BotKit did not acknowledge the message, with details like <endpoint>, <error code>, and <response time>.
Field
Description
Log
Description of the debug log. For example: getIndex is not defined.
Task Name
The task identified for the user utterance. Click the Task Name header to enable Group by Task.
Debug Point
The point or node in the conversation where the error is identified. For example: buildDataForCarousel.
Channel
The specific channel where the conversation occurred.
Language
The language in which the conversation occurred. Defaults to all enabled languages.
UserID
The end user’s ID. View metrics by Kore User ID or Channel User ID. Channel-specific IDs are shown only for users who interacted during the selected period.
Date & Time
Date and time of the chat. Sort by Newest to Oldest or Oldest to Newest.
Records pinned from Failed Tasks, API Calls, and Script Execution are displayed here. The fields available in the Pinned section pertain to Task Execution Logs.
Filter information by user utterances, intent, user ID, date period, channel, language, and custom tags. See Filter Criteria for more details.
Complete meta-information is stored for later analysis, including the original user utterance, channel, extracted entities, custom tags, and detailed Task Execution Logs.
Pin important records for later tracking. Pinned records appear on the Pinned tab.
Sort by Date and Time (Oldest to Newest, Newest to Oldest). Export insights data as a CSV file.
