Skip to main content
The Transactions section of the Skill Monitor service displays detailed information about system performance, active and completed transactions, as well as the stages of transactions for a specific skill. Tenant Administrators and Processing Supervisors can analyze this information to manage document processing for each individual skill — detect transactions with errors, identify error causes with the help of detailed transaction event logs, cancel transactions, or get transactions for manual review. Information in the Transactions section is presented in the form of graphs and a list of transactions. You can use the filters at the top of the page to specify the data to be displayed. The data can be filtered:
  • By the skill whose transaction you want to see.
  • By the type of transaction for which statistics should be displayed: all, processing or processed.
  • By the time period during which transactions are collected: 1 hour, 3 hours, 3 days, etc. The transaction list displays data filtered by creation date, while the Throughput graph displays data filtered by completion date.
Note: All active transactions will be displayed, even if they do not match the filter.
  • By the stage for which statistics should be displayed:All, Manual Review or Automatic.
  • By stage name.
  • By transaction status: All, New, Processing, Processed, Failed or Canceled.
The information displayed in the graphs will depend on the filters that you have set:
  • Throughput in every single point of time will display the number of transactions that have been completed up to that point.
  • Queue in every single point of time will display the number of transactions that have not been completed up to that point.
  • Duration in every single point of time will display the average time taken to process the transactions that have been created up to that point.
To view information for a specific part of the graph, hover the cursor over it. For example, you can use the peak of the Queue graph to see the number of uncompleted transactions was the highest. Graph information is updated once every few minutes. It is also updated when the page is refreshed and when the selected filters are modified. Besides the graphs, the page displays a list of transactions for a skill for a specified period. For each transaction, the following is displayed: its file names, identifier, current stage, stage assignee, number of processed documents, creation time, and duration. You can specify whether columns with additional transaction and document parameters (file name, file path, and source type) should be displayed. To do so, click the more options icon in the table header and select the appropriate parameters from the list. You can also use that list to manage columns for the other transaction parameters. Additionally, you can specify custom parameters and similarly specify which ones should appear in the transaction table: click the more options icon and select the Add column command. In the dialog box that will open, select the parameter type - Transaction or Document, and specify a name for the parameter. Additional parameters can be used for in-depth system performance analysis. For example, if documents from a specific source (e.g. mobile device) always take longer to be processed compared to documents from other sources, this may mean that the skill used to process documents from that source needs to be improved.
Note: Transactions are deleted after a period specified in the retention policy regardless of their status, with all related documents, as well as all recognized and extracted data also being deleted alongside them. The default storage period for a transaction is set to 2 weeks. Automatic deletion does not affect documents uploaded when setting up and publishing skills (training and demo document sets), since these documents are considered to be user data. You can also delete a transaction manually before its storage period ends using the Vantage API.
Tenant Administrators and Processing Supervisors can perform the following actions on each transaction in the list:
  • Get a transaction for manual review and process it in the Manual Review client. To do this, open the desired transaction from the list of transactions. If the task is opened by another user, a warning window will be displayed. You can use this window to either reject or get the task. If you reject the task, it will be returned to the queue. If you choose to get a task opened by another user, this task will be passed to you. All changes made by the other user will saved.
  • Send a transaction to the Manual Review stage and to another operator. To do this:
    1. Open the desired transaction from the list of transactions. The Manual Review client will open.
    2. To send the transaction to the next stage or operator in the Manual Review client interface, perform the actions described in Manually Reviewing Documents in ABBYY Vantage.
  • View the detailed event log to identify the event that caused an error. For more information, see section Workflow Events below.
  • Cancel a transaction. This may be required when a critical error occurs due to a faulty document upload. Completed transactions cannot be canceled.
Note: All of the actions above can only be performed by Tenant Administrators and Processing Supervisors. A Skill Designer can view transactions for all skills.

​
Workflow Events

If required, you can view a detailed event log for each transaction workflow. If the workflow is being held up at a specific step or if it has an error, viewing the detailed event log may help you identify the specific event that caused the error. To view the detailed event log, click the name of the appropriate transaction in the list, which will open the Transaction Event Log window that contains a list of all events for the selected transaction. You can use the event log search bar to find an event using its name. You can also use the Errors filter to view only those events that have errors.

​
List of possible workflow events

EventDescription
Workflow CreatedA processing flow has been created to start a transaction.
Workflow StartedProcessing started.
Job CreatedA task has been created as a part of a transaction.
Job StartedTask started.
Job CompletedTask completed.
Workflow CompletedProcessing completed.
Reprocessing startedProcessing restarted, as it was not completed within the allotted time.
Log MessageLog or error messages caused by Context.LogMessage or Context.ErrorMessage methods respectively in Custom activity and External System (Output activity) scripts. Messages written using the Context.LogMessage method are denoted by a warning character, and messages written using the Context.ErrorMessage method are denoted as errors.
To make sending detailed transaction event information to technical support or the system administrator easier, export the event log to a CSV file by clicking the Export to CSV button at the top of the Transaction Event Log window.