When a long-running script is interrupted or killed from the Script Editor, the UI may report that the task was interrupted, but the script continues running. This indicates that the editor’s cancel/kill path does not guarantee actual termination.

The issue is that the caller cannot distinguish between:

• “interrupt was requested”
• “the script actually stopped”

As a result, a script may continue executing after the editor reports interruption, and the underlying termination path may throw UnsupportedOperationException or otherwise fail to stop the thread. This makes timeout and cancellation handling unreliable for long-running scripts.

Expected behavior:

• an interrupt/kill request should either stop the script or clearly report failure
• callers should be able to tell whether termination actually succeeded
• cancellation should not be reported as successful if the script remains active