What the screen does not show
A portal may draw a table from one request, generate a file through another and check a form through a third. A person sees a page change. An agent that only sees the page can miss which change mattered, or mistake movement on screen for the operation itself.
More evidence for the workflow
When you show a digital worker a task, Ramain records the actions, the page states and the screenshots. Where the screen is not enough, it can add the page's network requests and console output to that record, so it can tell whether the important step was a click, a background request, a generated file or a hidden validation.
The workflow it produces is more precise about its inputs and outputs, and about how the task can fail.
Scoped to your session
This only applies to the browser session you started, in the systems you gave the digital worker access to. Whether it is used is a workspace setting, and like every run, what the digital worker did is recorded and can be replayed.