So my understanding is they will try to run as close as possible to the start of the minute whenever you scheduled the cron But yes they do not allow second granularity my guess as to why. AWS probably wanted to limit system load also most use cases for this are probably like batch processing, data backups or other stuff where second granularity isn’t needed. If you need second granularity you’d have to build some sort of workaround like having the lambda execute every minute and then have logic in the lambda to poll for your desired second
@@Hitchon I have 5 lambda functions, for each of them I had to recreate the cron job 3-5 times to make it run at 00-01 sec. sometimes you can create a cron job with a 00 sec run the first time. and it doesn't matter what time you created the cron job :) this is very annoying!!!
Thanks for the info.
Useful ..... Thanks
thanks for the information!
why doesn't the cron job run at 00 seconds? every new cron job runs at random seconds
So my understanding is they will try to run as close as possible to the start of the minute whenever you scheduled the cron
But yes they do not allow second granularity my guess as to why. AWS probably wanted to limit system load also most use cases for this are probably like batch processing, data backups or other stuff where second granularity isn’t needed.
If you need second granularity you’d have to build some sort of workaround like having the lambda execute every minute and then have logic in the lambda to poll for your desired second
@@Hitchon I have 5 lambda functions, for each of them I had to recreate the cron job 3-5 times to make it run at 00-01 sec. sometimes you can create a cron job with a 00 sec run the first time. and it doesn't matter what time you created the cron job :)
this is very annoying!!!
@@edengodman3178 yeah that sounds frustrating! But you were able to get it to work in the end ?
@@Hitchon yeah! after 5 tries :D