Break Out of Running Script in Framemaker

The only way I know how to do it is to just force quit FrameMaker. Of course, the best way is to make sure your code is robust enough to prevent runaways. The most likely cause are endless loop situations, but those usually show up in testing. For scripts that work on active documents and books, I will have my client test them on several documents before turning them loose on a book. Also, I never let a script save a document that it did not open, so I may tell the client to open all files in the book before running it on the book. That way, they can close the files without saving them. Of course, when in doubt, have backups done before running on production documents just in case.