I've set a custom trigger with execution frequency as Ongoing.
On the first initial run, it'll work properly. If I try to run it again on the same machine, it'll say "no policies were found for the "xxxxxxx" trigger.
I've tried flushing the log and re-running to no avail.
If I edit the policy that contains the custom trigger, and save it exactly as is, it'll work when I re-run the policy.
@kerouak / @sdagley I'm seeing similar behavior with 9.99. Policy scoped to a single computer, set to ongoing. The policy calls a script, that's it, and if I run it once and try to run it again later, "No policies found". There is no trigger set on the policy, as I am calling it using the ID (
jamf policy -id <idnum>). If I delete the computer and re-add, the policy runs fine.
I'll do some more testing today or tomorrow and if necessary I'll open a ticket with support. Anyone else opened a ticket on this?