Record automation execution

Automation enables you to perform complex business tasks swiftly and securely. If any of the scheduled automations fail or encounter issues, identifying the errors can impact the productivity. Recording an automation can help you review and resolve any errors that might have caused any runtime failure.

Note: Functionality to record automation execution requires the Enterprise Platform license. Contact your Automation Anywhere account representative for more information about this license.

Organizations can have multiple automations managing various tasks on a daily basis, and it can get difficult to monitor each and every one of them constantly. When you update Bot Agent to the latest version, all the automations that are initiated in the Control Room are recorded by default.

Administrators can select one of the following preferences for recording automation executions:
  • Only failed executions: Recording will be stored only when the automation execution fails.
  • All bot executions: Recording is stored irrespective of whether the execution is successful or failed.
Note: Option that an administrator selects will be the default selection for all other users in the Run Task Bot and Schedule Task Bot screens. However, users can change these settings while deploying the automation.

Run a bot | Schedule a bot

However, administrator can also delete any of the unimportant recordings to free up the storage space on database.

Considerations when recording automation: Keep in mind that recordings might be impacted in the following cases:
  • A total of 100 MB of storage space is available for automation recordings.
  • CPU overhead for encoding the last 5 minutes of automation recording might impact the execution time of the next automation if the execution time and the scheduled frequency are less than 5 minutes.
  • Automation recording might fail for deployments that are based on multi-user sessions (for example, with 5 user session system with back-to-back deployment).
  • While the automation encoding or uploading is in progress and the associated user session is closed or logged-off, the automation recording might fail.
  • When the device is in locked state or the device window is in minimized state, the automation recording might fail.

    The screen capture command might also fail in such instants and the automation must be executed again.

  • The duration for retaining the recordings depend on the default or custom values set in the Storage details field. The recorded files will be auto-deleted when the duration of the stored recording exceeds the value set in the Storage details field.

    For example, if you have set the timeline as 10 days, the recordings older than 10 days will be auto-deleted.

See the video below to understand the benefits of Record Automation.