Overview

When the automation needs additional context or clarification to proceed, it will raise a question. A question is an exception that requires user guidance to proceed.

Identifying Processes Requiring Guidance

There are two ways to identify processes that require user guidance.

🔎 Exception Center

To identify processes requiring guidance, navigate to the Exception Center via the left sidebar. There, you will be able to see all pending exceptions.

📧 Email Notifications

An email notification will be sent from Kognitos Automation when guidance is required. Click on Take Action in the email to be redirected to the Exception Center.

---

How to Provide Guidance

This section will overview how to provide guidance in Kognitos along with different exception types, resolution methods, and input options.

Exception Types

1. Provide data: The automation is unable to find a file or a particular data point from the document.
2. Automation error: There is an internal issue with the program and the automation is unable to proceed.
3. Translation error: The automation doesn't understand what's being asked, mainly due to syntactical errors.
4. Provide method: The automation understands what's being asked, but requires more detail to proceed.
5. Review data: The automation requires human review before proceeding.

Resolution Methods

1. Write in answer

This options allows you to type in any value for the requested field.

Note: For this option, your English doesn't need to be formatted as it would be for an automation—any value will work.

2. Upload files

This option allows you to upload a file in response. Click the icon and select a file from a local folder to upload.

3. Select from Document

This option lets you manually select the desired field within the document by clicking and dragging a box around it.

🚧

Syntax

To use this option, ensure you use the syntax get the <X> as a scanned document. For example:

get the file
get the file as a scanned document
get the document's <some-field>

Note: Do not usedocument as the value for <X>.

4. No Value

This option allows you to say "at this time no value is needed or necessary". This option is useful when a value is unavailable or not applicable. Internally, a dash ("-") will replace the value as a placeholder.

5. Retry

This option retries the failed automation step. It may be helpful if the exception was caused by a network error or a timeout.

6. Retry after an interval

The automation can be re-executed post a certain period of time, that can be determined by you.

7. Compute an answer

This method allows you to modify the automation to resolve the exception. Use the Mini-Playground to refine and test the automation without affecting the main process.

7. Skip this Step

This option bypasses the step in the automation. Skipping a step can lead to another exception if the step resolves a fact that is referenced later in the automation.

For example: An exception occurs with the message "Could not get a file as a scanned document". The user chooses the Skip this step option. Later, the automation attempts to reference the document, resulting in a new exception: "Please provide scanned document."

Special Options

For each resolution method, you have the option to mark each answer as:

• Secret
• Always use this answer for this department?

Secret

This option saves your answer as an encrypted secret. It can be viewed by admin users if saved as a Learning.

Always use this answer for this department?

This option sets the response to the error for that specific line of English to be applied across the department. This option is helpful for very common errors.

For example, if you are working with a system that often times out, using the Retry option could be a helpful option to set to be used across the entire department.