Until now, the GUI operation processes ware recorded by itself using the following resources. FFmpeg Optage - Desktop Video Recorder Activities - RPA Component | UiPath Marketplace
I was impressed that the recording function that UiPath previewed for the Enterprise version this time is very sophisticated compared to its own version. It is very easy to check in the Jobs tab in Orchestrator.
Although it is the “Save job execution recording” function, it may not be retrieved with some frequency.
First, I switched from my own recording function (FFmpeg) to UiPath’s “Save job execution recording” function in my GUI operation processes.
About 1 in 6 times the process wasn’t getting a recording everyday. Therefore, I checked the recurrence frequency by executing a trigger once every 30 minutes in a anothor PoC GUI operation process. I checked 100 jobs, but 8 of them were not acquired. I don’t know if this is an acquisition failure on the robot terminal side or a failure in the process of transferring recorded data to the cloud side. I have recorded more than 10,000 times for several years with my own recording function (FFmpeg), but I have never failed to acquire it. I am a user of the Community version, but I thought there might still be some quality improvements to be made as functions for the Enterprise version.
Test results are
Successful recording(92/100)
I’ll report back on what I find out after the incident.
I recorded and examined the normal process and the process when an event occurred with OBS Studio.
1.Normal Process is below
a) Create working folder with uuid
b) Output webm format recording files (nnn.webm) in units of 10 seconds (up to 18 files)
c) And manage the output order by outputting it to the list.ffconcat file (used in the order in which recorded files are combined when recording ends)
d) At the end of recording, perform the following processing.
One. Based on the list.ffconcat file that stores the output order, combine the recorded files and output a file called recording.webm
Two. Output the metadata.json file that stores the information of the recording start time
Three. Output thumbnail image thumbnail.png from recorded file
Four. Output log file ffmpeg-log.txt
Five. Upload prepared materials to Orchestrator(I didn’t know if the log file was also uploaded.)
Six. Delete the working folder
Failure process
When recording ends, the uuid working folder is deleted without outputting the combined recorded file, metadata.json file, thumbnail image thumbnail.png, and log file ffmpeg-log.txt.
My supposition
If the size of the last recorded file is 0kb, is it an implementation that causes an exception error in the merging process?
Recorded picture just before the uuid work folder was deleted
