Redefine Exception Handling: Teach Your Automations with Kognitos
Introducing a paradigm shift in Exception Handling, with Exception Center.
Despite the significant advantages showcased by automation, a major challenge remains in planning for and handling various exceptional scenarios.
Legacy process automations were created by software developers for business users. However, dealing with software maintenance and exceptional scenarios, such as unanticipated behavior has been a costly and labor-intensive process, often requiring software engineers. Although business users may understand what went wrong or what is going on, they are still at the mercy of code written by software developers.
With the advent of Generative AI powered automation solutions, platforms like Kognitos have gained the ability to allow users to engage with the system in natural language, redefining exception handling.
The video showcases how Kognitos allows users to teach their automations how to handle the exceptions themselves. The Platform’s newly introduced exception handling interface, the Exception Center ensures users can deal with these exceptions with unforeseen variables and complexities. Automation developers no longer have to build exception handling logic for each edge case that occurs.
Here’s how it works:
Common questions
What is conversational exception handling in Kognitos?
When an automation hits an unexpected situation, instead of failing, Kognitos surfaces the exception and lets you resolve it in plain English. That resolution becomes a Learning applied automatically every time the same situation occurs in future runs.
What are Learnings and how do they reduce manual work?
A Learning is a recorded exception resolution. Each exception you resolve teaches the automation. After a few runs, the system handles the same edge cases automatically. Manual intervention compounds downward toward zero as the Learning library grows.
How does Kognitos exception handling differ from traditional automation tools?
Traditional automation tools fail on exceptions and require developer intervention to patch the script. Kognitos surfaces exceptions to business users who resolve them in plain English, with no code changes and no IT tickets. The resolution itself becomes the fix.
Which workflows benefit most from conversational exception handling?
Document-heavy workflows with format variation: invoice processing, claims handling, bank reconciliation, PO matching, and any process where input documents arrive in slightly different formats each time. These are where traditional RPA breaks most often and where Kognitos excels.