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

Missing some schedule instance on sidekiq-cron #464

Open
Ramkumar0508 opened this issue Apr 16, 2024 · 2 comments
Open

Missing some schedule instance on sidekiq-cron #464

Ramkumar0508 opened this issue Apr 16, 2024 · 2 comments
Labels

Comments

@Ramkumar0508
Copy link

image (1)

Sidekiq Version: 5.0.0
Sidekiq-cron Version: 1.2.0

Hello,
We've observed that some worker schedule instances are missing. This inconsistency occurs regardless of the cron timing configuration. Initially, we set the cron expression to run the worker every hour (1 hour). However, we noticed delays where the worker would sometimes execute after 4 or 6 hours, deviating significantly from the intended schedule. Subsequently, we adjusted the cron expression to a more frequent interval of 30 minutes, but the issue persists.

Could you please advise on potential causes for this behaviour and suggest any solutions?

@markets
Copy link
Member

markets commented Apr 16, 2024

Hey @Ramkumar0508,

The versions you're using are a bit old. We only officially support Sidekiq v6 and v7 (see our CI: https://github.com/sidekiq-cron/sidekiq-cron/blob/master/.github/workflows/ci.yml#L12).

I suggest to upgrade to at least the latest Sidekiq v6 and latest Sidekiq-Cron (which is v1.12.0: https://github.com/sidekiq-cron/sidekiq-cron/releases/tag/v1.12.0) and try again. Hope you understand that 🙏🏼, but we can't test your scenario in such old (and EOL) versions.

@Ramkumar0508
Copy link
Author

@markets Thanks for your message. We will upgrade the sidekiq and verify the changes.

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

No branches or pull requests

2 participants