Hi, many repetitive processes have certain exceptions and rare situations when a rule-based logic breaks, typically due to variability of incoming data (e.g. robot finds a text instead of a number in certain template field). Our approach is to (1) provide users with custom exception/error handling logic, e.g. evert robot logic step has an "exception" branch that activates of the bot can't correctly complete the activity; (2) be able to activate "human in the loop' function to bring in user when needed; (3) be bale to work with unstructured data like random invoices to minimize the need for (1) and (2)
