Hey,
Thanks for reporting that. This is an issue we are aware of and it is fixed in the latest version. See Bug #36130: job invocation shows wrong info after remote execution job I’m going to talk about it more in this week’s community demo if you want to get more details.
1 Like