If you’re trying to run a workflow that is attempting to call data that is being blocked by a Privacy Role it would be good to point that out instead of showing (empty).
Identifying what role is causing the restriction or (empty) is very helpful to identify what the problem is plus test security settings in general. If something is being protected it would be good if the Role protecting that data is displayed.
I’ve had two instances now where I’m scratching my head trying to figure out what’s wrong when it was a Privacy role all together…
If it were identified you can go right to the source of the problem.