I implemented a bot to send scheduled daily notifications. Despite run_repeating working fine, run_daily ignores my set time and fails silently. I’m unsure if I misconfigured the timezone.
I encountered a similar issue when working on a daily notification feature in my bot. I realized that the primary complication stemmed from mismatches between my bot’s scheduled time and the server’s local time. After some trial and error, I determined that explicitly creating datetime objects with defined timezones for scheduling helped clarify the expected run time. I eventually also checked the server’s logs to verify that the time was what I expected. In my case, ensuring the timezone alignment resolved the silent failure of run_daily completely.
Based on my experience, the issue with run_daily not executing as expected was related to the way datetime objects were handled, particularly regarding timezone information. I discovered that ensuring all datetime objects used in scheduling are timezone aware is key, especially when deploying on servers with different local settings. Converting times using pytz or a similar library made the difference. I also validated the scheduled times against the server’s log times, which confirmed that the discrepancy was indeed due to timezone configuration mismatches.
hey alice, i had simlar issues. my fix was to ensure datetimes had proper tz info. run_daily expects tz aware datetime objs so if they dont match, it fails silently. check your server tz alignment and that might fix it.
I encountered a similar issue when initially implementing run_daily to schedule notifications. My main problem was mixing datetime objects with and without explicit timezone definitions. This resulted in unexpected behavior because the job was comparing a naive datetime with a timezone aware one. Revisiting my code, I ensured that every datetime object used for scheduling was set with the correct timezone information. Using library-provided tools such as pytz to set and compare the times properly helped me avoid silent failures. It also simplified debugging, as I could then clearly see where the mismatch was occurring. This approach greatly improved the reliability of my bot’s scheduling tasks.