Closed DWecke closed 3 years ago
Yeah, it doesn't make sense to use at when frequency is 'minutely'. I probably should remove that from the documentation.
If you want to see more in the logs, consider putting options(echo = TRUE)
at the top of your Script_to_be_scheduled.R
script.
There is no such thing in cron which indicates 'once a specified time is reached'.
The most relevant use of at is frequency 'dayly' at = '14:56' to run every day at 14h56
Where in the documentation you see the usage of frequency = 'minutely' together with the usage of at?
Closing as there is no such thing in the documentation
My stack overflow question on this issue can be found here https://stackoverflow.com/questions/68012286/cronr-runs-only-once-frequency-set-to-minutely-then-doesnt-run-anymore-after/68076777#68076777
I am currently using cronR version 0.4.2. The documentation when you do ?cron_add shows examples where the 'frequency' and the 'at' arguments are both given variables however I ran into this issue when I tried to do the same. After commenting out the 'at' argument, the script started running every minute as expected.
"Script_to_be_scheduled.R" - Create's and outputs a file:
"Scheduler_test.R" - Create's and schedules the cron job to run every minute once a specified time is reached: