Skip to content
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

Jobs scheduled with use_local_timezone=True are executed twice #260

Open
waldner opened this issue Apr 8, 2021 · 3 comments
Open

Jobs scheduled with use_local_timezone=True are executed twice #260

waldner opened this issue Apr 8, 2021 · 3 comments

Comments

@waldner
Copy link

waldner commented Apr 8, 2021

I have the following scheduled job:

job = scheduler.cron(
    "1 12 * * *",                    # A cron string (e.g. "0 0 * * 0")
    func=tasks.myfunc,     # Function to be queued
    args=[],                         # Arguments passed into function when executed
    kwargs={},                       # Keyword arguments passed into function when executed
    repeat=None,                     # Repeat this number of times (None means repeat forever)
    queue_name='my_default',  # In which queue the job should be put in
    meta={},                         # Arbitrary pickleable data on the job itself
    use_local_timezone=True          # Interpret hours in the local timezone
)

With rq-scheduler 0.11.0, which supposedly fixed #247, the job is scheduled twice: once at 12:01 local time as expected, and another one at 14:01 local time (CEST, currently UTC+2, so it's 12:01 UTC time).

This was referenced Oct 27, 2021
@lee-jian-hui
Copy link

did anyone find a fix here? or could someone point me in a direction to resolve this issue through any means possible.

@lee-jian-hui
Copy link

FYI: this also happens when use_local_timezone=False and imo is a pretty big issue

@newmancu
Copy link

Maybe the problem is in repeat=None. You can check this #317

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants