☑ cool new feature
☑ could help many users!
☑ removes something that feels like a „bug“
☐ nice to have
☐ nobody needs it
What inspired this wish list request?
Some functions in Jmp take a very long time to get finished.
- There is a request to , because it can take hours to be executed.
- Another issue: Life Distribution. Depending on the size of the data table, the user has to wait for hours:
https://community.jmp.com/t5/Discussions/how-to-make-cumulative-probability-plots-in-JMP/m-p/717879/... - another application case: Database queries.
They can be executed in the background. But then the query cannot be included in a script. The next part of the script has to wait for the data to arrive.
Would be great if there was an option to interrupt the query if it takes too long.
For all these cases, it could help to cancel the activity after a specified Timeout interval:
What is the improvement you would like to see?
- Option:
For Try(), please add a possibility to specify a timeout interval. If the execution of the code takes longer, the script is stopped and the table is reverted to the initial state. - Please add a timeout parameter in the preferences.
if the user specifies a timeout of 10 minutes, If starting a platform or executing an action takes longer than 10 minutes, the execution is stopped.
For actions which alter the data table, the table is restored to the point before starting executing the action. This should be possible because most actions in Jmp have an undo function. I guess a recovery point is stored before starting the action?
Why is this idea important?
There is a Wish from 2020 with 79 Kudos: !
So, it seems that there is an extreme demand here, but it also seems to be extremely complicated to fulfill the users' wish.
The Timeout concept could be an easy solution.
Every user will accept to wait 10 minutes (and get a coffee - or two) instead of losing the results of many hours because an action in Jmp takes orders of magnitude longer than the user expected.
more wishes by
