Due to some latency with Jamf, I found that there is a potential situation where a properly scoped Self Service policy with the jss-progress.sh script could hang indefinitely if the policy it calls is no longer in scope. This results in the progress bar window being stuck on screen with no obvious way for the end user to force quit it.
Reproducibility: Anytime the jss-progress.sh policy has a trigger for a policy that does not include the machine the jss-progress.sh policy is being run on.
Due to some latency with Jamf, I found that there is a potential situation where a properly scoped Self Service policy with the jss-progress.sh script could hang indefinitely if the policy it calls is no longer in scope. This results in the progress bar window being stuck on screen with no obvious way for the end user to force quit it.
Reproducibility: Anytime the jss-progress.sh policy has a trigger for a policy that does not include the machine the jss-progress.sh policy is being run on.