Hi All, is anyone here tried the scheduled script to run every second? Like for example i run the scheduled script then the process has been done it will re-run the scheduled script again to check if there are new data to be process, if no new process then it will re-run until new data needs to be processed again. If anyone tried it, does anyone know why it suddenly stop the execution there's no error in logs just suddenly it stop the execution.

Is the next run of the scheduled script stopping the already running script? Or does it wait until the script stops running, before running it again on the next iteration?

This one: Is the next run of the scheduled script stopping the already running script. I don't know why it stop suddenly, or did i just used the maximum logs allowed for that log level (error)? I assumed it isn't the issue because it will remove only the old logs AFAIK.

Unless you're printing thousands of lines to the log, you shouldn't be hitting any limits

I'll try the multiple deployments when deployment1 is finished it will call the deployment2 and so on. Thanks for the input.

This is a really bad idea, you would not want to indefinitely block one of the queues up with a script that runs every single second.

I think there will always be a positive and negative idea on that design.