We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug Celery beat is not run, no jobs are scheduled.
To Reproduce Start the container with celery beat. See that no jobs get scheduled.
Expected behavior Jobs should get scheduled.
Screenshots N/A
Additional context Previously, we had problems with calling add_periodic_task with WRONG kwarg signature instead of `sig.
add_periodic_task
signature
The text was updated successfully, but these errors were encountered:
Fixing scheduling of Celery tasks (#72)
40591b6
Celery beat works now
[2022-02-09 08:00:00,014: INFO/Beat] Scheduler: Sending due task fileboxes.tasks.fileboxes_update_states() (fileboxes.tasks.fileboxes_update_states) [2022-02-09 08:00:00,027: INFO/MainProcess] Received task: fileboxes.tasks.fileboxes_update_states[8e158ef2-9200-4a49-b364-ec2e4c2146a6] [2022-02-09 08:00:00,684: INFO/ForkPoolWorker-2] Task fileboxes.tasks.fileboxes_update_states[8e158ef2-9200-4a49-b364-ec2e4c2146a6] succeeded in 0.6549682468175888s: None
Sorry, something went wrong.
87970c7
No branches or pull requests
Describe the bug
Celery beat is not run, no jobs are scheduled.
To Reproduce
Start the container with celery beat. See that no jobs get scheduled.
Expected behavior
Jobs should get scheduled.
Screenshots
N/A
Additional context
Previously, we had problems with calling
add_periodic_task
with WRONG kwargsignature
instead of `sig.The text was updated successfully, but these errors were encountered: