Recording - Preview release

Yes, I am on Enterprise Plan , Will try on my community plan and share the feedback.

Also , Welcome to the Community :slight_smile:


1 Like

@Adrian_Tamas ,

I tried this - This Worked Perfectly And I was able to view the Recording as Well . After some time when I attempt to RePlay the Recording - Is Says - An Error has occured . Attached Screenshot.

One feedback :slight_smile:

We can think of an Option to add a Filter Here - to Filter out the Jobs which has Recordings or we can Put some Symbol to differentiate the jobs with screenshot / Videos.

This is for the support people monitoring a lot of Jobs.


Thanks, we will look into this.

Thanks for the feedback, will see what we can do. Filtering was initially in scope but the team encountered some challenges in delivering it in v1.

Can we save the recording or share via emails to business groups?


Yes we have option to Play the Recording , we can play it in PIP and the same time Download the Same.


1 Like

Thanks Mukesh it helps

Amazing feature. Thanks

1 Like

Most desired feature in my organisation!!


That would be great to get the option to get record from failed transaction. Then this option would be usefull on queue level (not process). In that case if I would need to check some faulted item I could enable that option inside queue settings, clone the item and restart execution.


Thanks for the feedback!, it’s on our to-improve list.

1 Like

Is there any timeline, when it will be available in enterprise cloud orchestrator

1 Like

Hi. It will be included in the next Automation Cloud release. Looking forward to you trying it out and sharing feedback.

FYI - we will also present it in this months’ demo day. Hope you can join.

Can I ask why it’s only the last three minutes of the process? We have gone from using FFmpeg ( no longer seems to work with VMware machines, interrupting selectors, and doesn’t look to be non-legacy convertible) been looking for a solution for this and this seems amazing, but if it’s only the last three minutes we will miss most of our hours-long processes, and be able to watch it handle error reporting only. Needs to be expanded to the whole video and reduced for the process after 3 months to errors only.
will be interested to see where this goes.

1 Like

thanks Andrew for the question and feedback! As the main use-case of the video recording feature is to troubleshoot faulted jobs, last 3 minutes would cover most failures. When you say you will “miss hours-long processes”, what was the use-case for those hour-long recordings?

As the customer, it is essential for you to have a complete and accurate understanding of the processes running in your organization. Video recording the entire process provides you with the ability to watch and review all stages of the process, including identifying issues that occurred throughout.

While the ability to record the last three minutes of a job is useful in some cases, it is not a sufficient solution for identifying the root cause of an issue that may have occurred hours earlier in the process. By only recording the last three minutes of a job, you may miss important information that occurred earlier in the process.

Additionally, being able to review the entire process E2E and then focus only on the errors at your discretion provides you with greater flexibility and control. It also allows you to have a comprehensive view of the process, which is especially important when dealing with complex workflows that involve multiple systems and stakeholders.

Therefore, as the customer, you should have the ability to choose whether to record the entire process or only the last three minutes, depending on your specific needs. By offering a whole recording, UiPath provides you with the ability to have a complete and accurate view of your processes, which is essential for efficient and effective operations.


thanks Andrew for the detailed feedback!

I have previously developed and used a video recording scope activity and have been using it for a few years at my organisation. It was giving us an advantage over competitors but I see that will now be ending :stuck_out_tongue:

My advice, based on long experience, is you should provide a few extra features. I am willing to share my tips as if I no longer have the advantage with my video features I’d like the UiPath ones to be as feature rich as mine.

My screen recordings can have the frame rate configured, which can really help with file size since as low as 1 frame per second is enough.

I have all the log messages that occur whilst the recording is happening end up as colour coded subtitles on my video track. I can toggle the log level with subtitle tracks (Trace, Info, Error etc is each its own track), this is very nice, especially to see the red errors when they occur.

I have it so that I can control the highlight on screen, the option you can toggle usually only in Studio. In this way I can have it highlight elements even on unattended bots. I have this so it can be toggled on or off, its extremely useful for debugging to see what elements the bot found.

Because my activity is a scope activity, it is able to be used discretely. We use it to record each transaction and for certain phases such as ‘start up’ (logging in). We also use it in documentation for recording unit tests.

I think it would be great if you allowed similar functionality to record discrete parts of the process, via a scope activity, which could then get attached to the job in the same way.

If we apply it to the reframework we could then have a recording around the job startup, around any job restarts and around the job close, then, per transaction, a recording.

This level of granularity is extremely useful.
I’d also strongly urge you to consider allowing the video recordings to be stored locally rather than always uploaded to the cloud in order to satisfy nervous IT security people and also allow a longer data redundancy policy.


Hi @Adrian_Tamas
We used Screenshots property of job recording. In our case, the duration is 80 seconds and frequency is 3 seconds. With detailed;

Process start time : 11:21:45

Start time of getting first Screenshot : 11:24:20
Last time of getting screenshot : 11:33:05

Error time of getting screenshot : 11:25:34

As a result, we obtained 25 screenshots. What does the connection between duration and frequency to obtained this 25 result?