We have enabled Orchestrator Recording on our on-premise solution and have tested the functionality with the generation og Execution Media on our Orchestrator Server.
The recording seems to function as it should (as designed).
However as we always create our processes from a modified, robust RE Framework which uses State Machine and Try-Catches, then our processes (almost) always handles Application Errors generated in the process itself or generated in a specific processing of a Transaction. These kind of Appplication Errors does not trigger any recording (screenshots) so we still need to generate local screenshot handling per process.
We would like to suggest that the Orchestrator Recording feature is further developed to be able to handle Application Errors inside a running process (e.g. RE Framework).