I’m working with a large UiPath process that’s already running in production. Over time, we’ve added many change requests, but we don’t have proper documentation for the current version anymore.
Is there any way to reverse-engineer the process to understand its steps? Can we generate a process map or detailed process steps from the output logs, so it’s easier to explain what the production process is doing?
Extract the project somewhere locally. In case you have its source files (xaml), you can open in UiPath Studio for an easier visual analysis and step by step debugging.
If the sources are not present anymore, add for your robot user in Orchestrator the Verbose logging and try to review the generated logs to have an idea what it is doing.
I’m trying to build a lightweight way to reconstruct the step-by-step flow of any UiPath process running in production, with minimal effort but maximum clarity/accuracy. Could you suggest the most reliable approach?
Task Mining / Task Capture: My understanding is these are for discovery on user desktops and not intended for unattended production flows. Can they help in my scenario at all?
Log-based mapping: Generate a process map using Orchestrator logs and Maestro (UiPath BPMN agentic AI tool).
Marketplace/Community: Are there ready-made components or templates that can turn robot logs into a step-level process map?
Constraints: Prod is unattended; no screen capture is allowed. I haven’t tried these options yet, so concrete steps, architecture pointers, or sample queries would be highly appreciated.
Goal: Least effort now, but high clarity and accuracy in understanding the actual production flow.