-
Notifications
You must be signed in to change notification settings - Fork 622
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Midnight problem #400
Comments
@TeodorKolev Hi, I just want to make sure I understand the problem you're having. The cron runs normally and the |
@ncb000gt exactly |
I setup a test that should exemplify the issue you noted and it seems to pass fine. Locally. Obviously, it's a test and not the real env...so, I also ran a test by changing my machine time to 11:59:50, and the cron triggered when expected.
Note that I'm in EST, hence the difference in the time representation. So, I have a couple of questions. Is it possible that the endpoint you're trying to hit is doing something at midnight? I've known places to put an automatic restart into systems for one reason or another, but this might be the reason for the delay and subsequent timeout you're seeing. Did you add any logging to the beginning of your onTick callback or the module itself to see when the onTick itself actually fires vs the timeout response? Let me know. Hopefully this is helpful, and I'm going to commit the test for tracking purposes. |
Signed-off-by: Nick Campbell <nicholas.j.campbell@gmail.com>
this issue is described in a passing test so I'm going to close it for now. feel free to reopen it if you're still experiencing this issue |
Everything works fine till midnight. Then cron job begin to produce timeout requests. Server time is set to UTC. I have also tried with different timezones specified, or without timezone. Same error results. Socket hang up on my requests after midnight.. Every cron tick after midnight is fired with couple of minutes delay and it's http inner method response produce
TimeoutError: ResourceRequest timed out.
Does anyone has any idea why it breaks after 00:00?node-cron version: 1.6
The text was updated successfully, but these errors were encountered: