Recording Service

Common Issues

  1. Recording Service performance is lower if using HDD only or SSD and HDD for storing the PostgreSQL database.
  2. We do not recommend storing logs on the Recording Service server for more than a week. After you submit logs to Timeline, you can backup logs to another server (if necessary) and remove them from the Recording Service server.
  3. After the Recording Service upgrade is complete, the list of logs on the Recording Service website will be empty. It may take some time to display all existing logs. Please wait a couple of minutes, and the logs will gradually come into view.
  4. When upgrading Recorder Service from version 6.0 to 6.1, you may consider uninstalling the previous version first. In this case, while upgrading the database will not be updated to version 13.
  5. When upgrading PostgreSQL to version 13, the installation process takes more time, as it includes copying the previous database.

I'm trying to start a recording, but the recorder does not change the status to "record".

A user may forbid action recording by clicking Disable in his/her Recorder menu in the system tray. This will stop a record and block recording control on this instance via the Recording Service UI. The recorder continues to display on the Recording Service website in the recorders list. Its status is online, but the status does not change to recording after you click Start and then Refresh List.

To start or resume recording using the Recording Service interface, the user must enable recording by clicking the Enable button in his/her Recorder menu in the system tray.

Recording on the selected Recorder has started, but logs are not reflected in the UI.

After you click the Start button, make sure the recording has launched. To do this click the Refresh list button and check the recorder status changed to the recording.

Recorded events are saved to logs and sent to the server for processing. When processing is complete, the logs are displayed on the Logs tab. New log may take some time to display in the Recordings tab.

Logs are partially uploaded, or upload fails.

There are some a limitation to upload logs: unable to upload logs, if the total number of unique events in logs exceeds 10000. If the limit exceeds, an attempt to upload logs fails with an error: The selected logs have more unique events than the allowed limit.

To solve this issue, reduce the number of logs being uploaded and try again. To check the number of unique events in one log:

  1. Go to Logs
  2. Click logs ID and check the UNIQUE EVENTS field.

22.02.2024 17:28:05

Usage of Cookies. In order to optimize the website functionality and improve your online experience ABBYY uses cookies. You agree to the usage of cookies when you continue using this site. Further details can be found in our Privacy Notice.