A looping or paused by a conflict PSOS 'session' can only be cured by closing the file and throwing other user off. I feel we need limits/tools that can be set that are very similar to server scripts
Specifically, I think the appropriate place to define a time-out for PSOS scripts is the Perform Script On Server script step, not the Admin Console. Manually stopping a PSOS script from the Admin Console should definitely be possible, but the server doesn't have the context necessary to automatically distinguish between a 4-hour runaway script and a 4-hour script that just takes a long time to run even when it's working correctly.
I agree there can be a huge range of expected run times, from 1 second to 10 hours. We can already build soft time limits into scripts that can terminate before an entire job is done. However, having some way to define a hard limit would be an excellent protection against design flaws.
I think I might go further than jbante, and claim that the best place to impose a time limit on a script is in itself. The calling script MAY know how long it expects a sub-script will take, but certainly the script itself has the knowledge of it's designer to inform a reasonable expected run time.
Borrowing from another environment, a self imposed Set Time Limit [ ] script step could be performed by a script before it gets into the core job. A watchdog style timer could even be reset or tuned in a multi-stage job. Maybe a file or server wide configuration could be used as a default and/or an upper limit. The upside here is that this script step could also be beneficial to areas outside of PSoS.
Retrieving data ...