> Thanks for your question. Can you highlight where it fails? Is this agent side (so the delegated machine) or is this on the server side? Do you have a bit more details on the ListAgents task? I wonder if we are getting a more opaque permissions error when something nested is indeed failing.
This fails on the agent side, when calling into the agents endpoint the server responds with a 403 “User does not have ListAgents permission” error when the job gets run via scheduler
> I’ll dig in a bit more on my end here to see if I can find out “who” is attempting to auth.
Thanks! I’m wondering if there’s some default service account that’s missing the listagents permission or something since it works when manually run and is able to call into the devices endpoint when run via scheduler