Keter generally watches an application and will restart it if it finds a change in the watched file.

If though for some reason the extracted binary passes the sanity checks, and the respective hosts are reserved, yet starting the binary results in "Process restarted too quickly, waiting before trying again" for 18 times, keter logs "Forgetting host reservations for app ..." and any subsequent change to the .keter bundle is noted as "watched file modified: ..." but the app is not extracted, sanity checked,... basically the log will just start having a "watched file modified: ..." line for each new upload but meter won't try the new bundle.