Custom trigger/could not connect to the JSS errors

bbot
Contributor

As of this morning, there were 3 machines that are failing to connect to the jss and running a custom trigger. The last successful that was ran by a user was at 7:30 PM last night.

<br/>Checking for policies triggered by "OfficeUpdate"...<br/>Could not connect to the JSS. Looking for cached policies

On my own machine, I tried sudo jamf policy - trigger OfficeUpdate and it works as expected. Any idea why some machines would work, and others wouldn't?

1 REPLY 1

stephanpeterson
Contributor

@bbot Did you ever get anywhere with this? I'm seeing a similar issue, but a different context.