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

[Bug]: repeatable jobs not working with python #2772

Open
1 task done
jaredmcqueen opened this issue Sep 17, 2024 · 4 comments
Open
1 task done

[Bug]: repeatable jobs not working with python #2772

jaredmcqueen opened this issue Sep 17, 2024 · 4 comments
Labels
bug Something isn't working

Comments

@jaredmcqueen
Copy link

Version

5.13.0

Platform

NodeJS

What happened?

according to the docs:

Every time a repeatable job is picked up for processing, the next repeatable job is added to the queue with a proper delay. Repeatable jobs are thus nothing more than delayed jobs that are added to the queue according to some settings.

I have tried both cron schedule pattern and every. Both create the repeated job scaffolding in redis, and both jobs work on the first run

after the first job run, no new job is rescheduled, so jobs only ever repeat once.

image image

How to reproduce.

create a repeatable job in typescript

pull the jobs in python

jobId does look different with repeatable jobs - like this:
jobId='repeat:dec4ba3039956b6560feae8ac0a67850:1726582010000

Relevant log output

N/A

Code of Conduct

  • I agree to follow this project's Code of Conduct
@jaredmcqueen jaredmcqueen added the bug Something isn't working label Sep 17, 2024
@roggervalf
Copy link
Collaborator

hi @jaredmcqueen, repeatable jobs are not currently supported in python version. Still working on the next breaking change for node version, so probably after that we can revisit this feature request

@jaredmcqueen
Copy link
Author

@roggervalf thanks for the update. What kind of timeline do you have in mind? Huge fan of this project and would be willing to help speed it along any way I can. Let me know what I can do to help.

@roggervalf
Copy link
Collaborator

hope that this week we can merge the next breaking change. Then we need to update pro versión and after that we will have time to revisit new feature request. So probably in 3 o 4 weeks.

@jaredmcqueen
Copy link
Author

hey @roggervalf just checking in after a few weeks. Was thinking about writing a workaround for python / cron. Holler if you have a timeline for true implementation. Again, I can help where needed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants