Custom trigger Policy not reporting to JAMF

New Contributor III

I've noticed that while launching at cascade a sequence of policy (each policy will call the next one by custom trigger), while some of them would report to jamf, at any moment, I'm not then able to see the rest of them in the device's History.194d9357f007467dab702e120114d733

Even if the device is effectively deploying them, policies do not report..what I've also noticed is that if (from device) I try to run "sudo jamf policy", this trigger seems to be eternally launched..
..and finally policies on the device seems to be someway pretty slow or even stucked..? Don't know how to determine that..

Even a "recon" does not let me know anything about what policies did or did not on the History...

Does anyone know about this issue?