Ok, the issue is not from Jamf Connect.
Before deploying Jamf Connect, we send a message to notify our users using a Jamf Helper script.
The problem is that when we use Jamf Helper when no one is logged in (on login window), it "blocks" check-ins.
To unblock the situation we must empty the folder /Library/Application Support/JAMF/tmp
Do you know what is the best method to use Jamf Helper to start immediately at check-in when a user is logged in or only start at next login if no one is logged in?
I'm a little newbie in scripting and I suspect that I'll have to use the launchagent but I can't find the right method.
Thank you for your help