Portfolio |

Guidance Center

Sun, 01 Feb 2026 00:00:00 +0000

Overview

When a Kognitos automation requires additional context or clarification to proceed, it raises an exception. An exception is an error or unexpected condition that prevents the automation from completing successfully.

Exceptions are resolved through guidance - input provided to the system on how to proceed. Using the Guidance Center, you can quickly provide guidance across automations to keep them running smoothly.

Exceptions

Exceptions are issues that prevent an automation from completing successfully. They occur when Kognitos encounters an unexpected condition, such as missing or invalid data, failed integrations or connections, and scenarios it hasn’t been taught to handle yet.

Types

Exceptions are grouped by the following types:


System Errors	Issues related to the Kognitos platform or internal processes. These are typically resolved by the Kognitos engineering team, and you'll be notified when they're fixed.
Configuration Errors	Issues with missing credentials, permissions, or integration settings that prevent your automation from accessing external systems. Example: Missing API key for an integration; authentication credentials have expired.
Value Errors	Missing or unclear data that prevents the automation from proceeding. Example: A required field like "Invoice Number" is missing from a document, or a value appears in an unexpected format.
Validation Errors	Issues where the automation needs confirmation that a condition or business rule has been met. Kognitos automatically classifies validation-related exceptions into this group for faster triage. Example: Verifying that a contract clause meets company policy requirements, or confirming that extracted data passes a business rule check.

Using the Guidance Center

Access the Guidance Center from the left navigation menu. It displays all open exceptions across your workspace, organized by automation and exception type.

Dashboard

When you open the Guidance Center, you’ll see a summary dashboard:

Metrics

The dashboard displays the following metrics to help you monitor automation health:

Metric	Description
Auto-completion (STP)	Percentage of runs that completed without manual intervention.
Runs Need Action	Number of runs currently paused and waiting for guidance.
Total Completion	Overall success rate across all automation runs.
Runs This Week	Number of automation runs in the current week.
Exception Rate	Percentage of runs that raised exceptions.
MTTR (Mean Time to Resolution)	Average time it takes to resolve exceptions.
Run Status	A visual chart that shows your automation performance over time, color-coded by resolution type: Auto-completion: Runs completed without manual intervention. Manually resolved: Runs that required your input to complete. Action needed: Runs are currently waiting for your action.

Action Items

An action item is a task created when one or more runs are affected by the same exception. The Guidance Center groups these runs by exception type, allowing you to review and resolve the issues in bulk, rather than one run at a time.

Each action item shows:

Name: The name of the issue that occurred (Missing Values, User System Error, etc.)
Priority: The severity of the automation exception
Run count: How many runs is this exception affecting
Automations: A list of automations that raised the exception

Selecting an action item lets you view the affected runs, review details, and provide guidance in bulk. Click on Start review to review the impacted runs and provide guidance.

System Issues

System Issues are internal platform errors that are being handled by the Kognitos engineering team.

Note

No action is required from you for system issues - Kognitos will handle them accordingly.

Exception Routing

Mon, 01 Dec 2025 00:00:00 +0000

Overview

Exception routing is a process configuration setting in Kognitos. It allows agent admins to configure assignment and notification rules for exceptions.

When a process encounters an (a question requiring guidance), these rules ensure that the right person is automatically assigned to handle it and that the appropriate team members are notified.

Configuration

Agent admins can configure exception routing for a given process, including the following settings:


Exception Assignment	Specifies who is automatically assigned to handle exceptions.
Email Notifications	Specifies who receives email alerts when exceptions need guidance.

How to Configure Exception Routing

Follow these steps to configure exception routing for a process:

1. Select a Process

Navigate to Processes and click on the process to be configured.

2. Exception Routing

Click on the menu ⋮ in the top-right and select Exception Routing.

Warning

The process must be in draft mode. If the process is published, click Edit first.

Exception Routing Menu Option

3. Exception Configurations

Configure the following details, which may be updated at any time:

Field	Description
Exception Assignee (Required)	The user(s) to assign to handle exceptions for this process. At least one user is required.
Notify Members (Optional)	The user(s) to notify via email when exceptions need guidance. This is optional and may be left blank.

Note

Only collaborators of the agent can be selected as assignees.

To add additional users, go to Settings → Invite Users → Add Collaborator.

Exception Configurations

4. Save and Publish

Press Save to apply your configuration changes. Then, publish your process to make the changes live.

Examples

1. Basic Assignment

In this example, exceptions go to the process creator with no notification recipients.


Exception Assignee	john.doe@company.com (Process Creator)
Notification Recipients	None

2. Specialized Handler with Team Notifications

Here, exceptions are assigned to the process creator while the team lead and backup get email notifications.


Exception Assignee	jane.smith@company.com (Process Creator)
Notification Recipients	team-lead@company.com, backup-person@company.com

3. On-Call Assignment

Here, the current on-call person is assigned exceptions while the manager stays informed through email notifications.


Exception Assignee	oncall@company.com (current on-call person)
Notification Recipients	manager@company.com

Exporting and Importing Agents

Wed, 01 Oct 2025 00:00:00 +0000

Overview

Kognitos supports the ability to export automation agents from one environment and import them into another. This allows you to move published automation content across agents in a controlled way.

Exporting an Agent

Exporting lets you download a snapshot of an agent’s published state. The export includes only published processes, learnings, and books — draft processes, playgrounds, and configuration credentials are not exported. Anyone with access to the agent can export it.

How to Export an Agent

1. Navigate to Agents

Open the agent menu and select View All.

2. Select an Agent

Check the box next to the agent you want to export.

3. Start Export

Click on Actions, then select Export from the dropdown.

4. Confirm Export

In the confirmation popup, click on Export again. This will download a .json file containing the agent’s current state, which can be later imported into a new or existing agent.

➡️

Importing an Agent

You can import an agent using a .json file generated from the export process. There are two ways to do this — into a new agent or into an existing agent. All imported items are added as drafts. The agent’s published content is not affected unless you review and publish the imported content.

Import into a New Agent: Use this option to create a new agent.
Import into an Existing Agent: This option allows you to update an existing agent and is available only to agent admins.

How to Import an Agent

1. Navigate to Agents

Open the agent menu and select View All.

2. Start Import

Click on Import to start the import.

3. Add Import Details

Upload a .json file of an exported agent.
Choose one of the following options:
1. Select Create New Agent and provide a name for the new agent.
2. Select Import to Existing Agent and select an existing agent from the dropdown menu. Note: This option is only available to agent admins.
Click Next to continue.

4. Review and Confirm

Review the summary of the import and click Import to finish importing.

Note

By default, all items are selected for import. You can uncheck items to exclude them.

➡️

Kognitos Release Notes: 8/1/2025

Fri, 01 Aug 2025 00:00:00 +0000

Save Dashboard Insights as Images

You can now download a PNG image of any individual metric in the . Whether you’re preparing a slide deck, building a report, or updating your team, you can easily share your insights from Kognitos.

BDK Books Can Now Ask Questions

We’ve expanded our with a new feature that allows you to ask questions in BDK Books. Using the new ask() method, your Book can request information - like a date, a username, or any other piece of data.

Enhancements

Abort Long-Running Guidance: Users can now abort long-running guidance computations that are taking long to process.
Extended Character Limits: The character limit for a single learning has increased from 10,000 to 15,000.
Process Widget Search: The process widget dropdown now includes a search bar.

Resolved Issues

Agent Imports: Resolved an issue where large agent imports caused a timeout error. We’ve also improved the import process to be significantly faster.
Process Creation: Resolved an issue where the Create Process button in the Playground was disabled if the first line in the automation was empty.
REST API (v1): Resolved an issue where invalid requests to the legacy REST API caused internal server errors.

Defining Data

Fri, 15 Nov 2024 00:00:00 +0000

Info

This guide describes Klang, Kognitos’ natural-language-based syntax for building automations. It allows you to build automations by writing instructions as if you were describing them in words.

Overview

In Kognitos, defining data refers to naming a specific piece of information, allowing it to be stored, referenced, updated, and passed between steps within an automation.

Every data element (also referred to as a fact) consists of two parts:

A that identifies and labels the data.
A , which represents the information itself. Values can be singular or plural.

Defining Singular Data

To define a singular data element, use “is”:

<name> is <value>

Defining Plural Data

To define a plural data element, use “are”:

<name(s)> are <value(s)>

Examples

In this example, the customer is the data name. It is assigned the singular value “John Smith”:

the customer is "John Smith"

Here, the items is the plural data name. It is assigned the plural value of the documents.

the items are the documents

In this example, the fruits is the plural data name. It is assigned a list (plural) of fruit values:

the fruits are the apple, the banana, the orange

Warning

Make sure singular names pair with singular values, and plural names pair with plural values! For example, you wouldn’t write “the fruits is the orange”. Instead, you would write: “the fruits are the oranges”.

Data Names

Data names define how information is labeled and referenced. The following rules apply:

1. Begin with “the”

Data names must be prefaced with the. For example:

the email

the phone number

the primary username

2. Names can be Simple or Descriptive

Data names can be simple or descriptive. Adjectives can be used in descriptive names to provide additional clarity or context. For example:

Simple Name

the message

Descriptive Name

the very special user greeting message

Data Values

Data values can be singular or plural. Possible data types include numbers, text, dates, lists, or references to other data elements.

1. Numbers

Numeric values can be assigned to data such as age, balance, or rates. For example:

the age is 21

the bank balance is $120.20

the interest rates are 5.67, 6.25

2. Text

Text values can be words, sentences, or phrases. They can include any characters—letters, numbers, symbols, or spaces—as long as they are enclosed in double quotes (""). For example:

the message is "Welcome to Kognitos!"

the username is "i-like-to-automate-123"

the announcement is "We're so glad you're here. Let's build something great together."

3. Dates

A date value represents a specific calendar day, such as a due date, birthday, or event date. Be sure to enclose date values in double quotes (""). For example:

the due date is "2024-11-05"

the project start date is "January 1, 2024"

the birthday is "March 22, 1990"

4. Lists

To define a list, separate the values by commas. For example:

the test scores are 95, 86, 100, 77, 65 and 99

the coupon codes are "SAVE20", "SALE2024", "HAPPYHOUR" and "JUST4U"

the email addresses are "john@gmail.com", "johnny@yahoo.com" and "johnsmith@aol.com"

5. Referencing Other Data

The value of a data element can also be a reference to another data element. In these cases, the data value is set to another data name. For example:

the username is the customer email

the documents are the receipts

the approver is the manager

Warning

Note: You can only reference another data element if it has been defined earlier in the automation.

6. The Above

When a data element’s value is set to the above, Kognitos makes a copy of the value from the previous lines in the automation:

<data name> is the above

Examples

In this example, the backup email is assigned the value john@example.com.

the customer email is "john@example.com"
the backup email is the above

Here, the invoice total is assigned the value 150.

the order total is 150
the invoice total is the above

In this example, the file is assigned a copy of the above file in the automation.

the file is the above

Reassigning Data

Use the use keyword to reassign a data element, which copies the reference to the original data value:

use <data value> as the <data name>

Warning

Overwriting Data: Updating a referenced data element can overwrite previous data — see for more details.

Examples

In this example, the registration date is reassigned the value 11-05-2024.

use "11-05-2024" as the registration date

In this example, the order name is assigned a copy of the reference to the last name, meaning it will point to the same value.

use the last name as the order name

If the last name changes, the order name will also change, because it references the same value. When the last name changes to Smith-Brown (line #3), the order name also changes (line #4):

the last name is "Smith"
use the last name as the order name
the last name is "Smith-Brown"
the order name

Release Notes: BrewBuddy v8.3.0

Tue, 18 Jun 2024 00:00:00 +0000

New Features

The Brew Timer is finally here! This is a new feature that allows users to set timers directly from the recipe screen, leading to a more seamless and precise brewing experience. Check out for more information.

Bug Fixes

Resolved an issue with images not loading properly or appearing blurry.
Resolved an issue where the temperature setting defaulted to 0.
Resolved inaccurate unit conversions on the recipe screen.

What’s Brewing on the Horizon?

Coming soon is the Brewing Events Calendar - a newly centralized location for all upcoming coffee events, workshops, and festivals 📅
Enhancements to the Brew Timer, including:
- Dark-mode display
- Multi-step brew timers
- Customizable timer presets

Note

BrewBuddy is a fictional app for demonstrational purposes only. It represents an online platform that provides brewing tips and step-by-step guides to empower coffee enthusiasts.