As @commensal mentioned, this “stop after 10…100” loops is a known issue. But we are making progress fixing it. We have now a way to create it, so fix should be available in the near future.
That said, if you want to run a script truly 24/7 I recommend that you use the command line. This allows you to check on the return value. And if Kantu or Chrome gets stuck, you can simply kill the process and continue. Here is a sample script that does this:
PS: With this script, when the “freeze issue” happens, then Chrome gets closed and the next loop starts, so the work continues.