-
I am in the process of upgrading to celery 5.x, and since there is no longer a I am logging info from the function that sets up the Subsequently, however, celery beat just sits and does nothing. beat never sends any messages, and as a result, celery worker never executes any scheduled tasks. In
Any ideas what I might be doing wrong and/or how to diagnose the problem? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
I found the problem. I was creating an instance of In the |
Beta Was this translation helpful? Give feedback.
I found the problem. I was creating an instance of
crontab
to validate values and then copying values from the properties of thecrontab
instance to fields of theCrontabSchedule
instance, but the properties ofcrontab
areset
objects. When writing those values to string fields, we get therepr
of theset
as the values, and those are not valid.In the
all_as_schedule
method in schedulers.py, that results in aValueError
which is caught and ignored, so the task is silently not added to the schedule.