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

---

I found the way and I'm ashamed it's so simple.
Just deploy the jamfhelper script in 'Recurring Check-in' / 'Once per user'.

Thus the script will not trigger closed session.

Thank you

---

Check-in will happen when the device re-detects the network and is active,
user login.

This will also depend on how you sent up your check-in policy.

But if you want to force it you can manually run a recon either via SSH, or
manually at the terminal:

So I would say this is normal behavior.

Thank you.

--
This e-mail is only intended for the person(s) to whom it is addressed and
may contain confidential information.  Any unauthorized review, use,
disclosure, or distribution is prohibited. If you received this e-mail in
error, please notify the sender by reply e-mail and then delete this
message and any attachments from your system. Thank you for your
cooperation.

---