Policy Time-out Threshold?

Valued Contributor II

I am experimenting with a a new policy that runs a bash script. In that bash script, I present an AppleScript (osascript) dialog box that prompts user for info, with a timeout of 5 minutes (300 secs). If no input occurs in 5 minutes the AppleScript stops and the Bash script exits with 1. The error is logged to acknowledge that the time-out occurred for later troubleshooting.

I have never designed a 'time-sensitive' policy or script before, and wasn't sure if Jamf policies have time-out thresholds.

Can a Jamf Policy run for this long without killing the bash script or timing-out?