Open arbazkiraak opened 5 years ago
I found the same problem. Is it a bug or is it supposed to be like that?
Hi @naturalbeau ,
I'm not really sure if it's a bug or supposed to work like that. Let's wait & see what the community has to say.
is it a celery bug or celery beat? could you try with the latest celery / master branch with dj-clrybeat master?
I'm trying to fix it. My environment: …… celery==4.2.1 Django==2.1.3 django-celery-beat==1.5.0 django-celery-results==1.0.4 django-timezone-field==3.0 …… Only in this way can it work. CELERY_ENABLE_UTC = True CELERY_TIMEZONE = 'UTC'
If I configure it like this Time zone and cron jobs does not take effect CELERY_ENABLE_UTC = False CELERY_TIMEZONE = 'Asia/Shanghai'
be fidgety……
Good day! Have the same problem with selery-beat.
I ran several tasks for testing - starting every 1...10 minutes, hours, days. And tasks for every 8,9,10 days launching wasn't been executed.
I running Celery and Beat in two Docker instanses. My Celery configuration:
CELERY_TIMEZONE = "Europe/Moscow" CELERY_TASK_TRACK_STARTED = True CELERY_TASK_TIME_LIMIT = 950400 CELERY_BROKER_URL = 'redis://redis:6379/0' CELERY_RESULT_BACKEND = 'django-db' CELERY_BEAT_SCHEDULER = 'django_celery_beat.schedulers:DatabaseScheduler' CELERY_TASK_RESULT_EXPIRES = None CELERY_BROKER_TRANSPORT_OPTIONS = {'visibility_timeout': 950400}
Hello Community,
Regarding : https://stackoverflow.com/questions/54497785/celery-interval-schedule-doesnt-executes-on-given-interval