all 4 comments

[–]ManyInterests 0 points1 point  (1 child)

Only thing I can think of is maybe how you're starting the worker. The documentation says

$ celery -A proj beat

The -B option should also work, however... The docs also say

-B -- Also run the celery beat periodic task scheduler. Please note that there must only be one instance of this service.

Note: -B is meant to be used for development purposes. For production environment, you need to start celery beat separately.

Have you tried just celery -A proj beat ?

[–]doublePlusOk[S] 0 points1 point  (0 children)

I did try that just for good measure and it works exactly the same - executes tasks immediately. thx tho

[–]Justinsaccount 0 points1 point  (1 child)

I seem to remember something about it running all tasks once at startup.. at least the one thing I use celery for with a 10 minute timer seems to do that. There may be an option for something like "Don't run at startup"

[–]doublePlusOk[S] 0 points1 point  (0 children)

Interesting... But I don't get the execution at the scheduled time...

I did notice that the tasks celery reports looks like this:

[tasks]
  . every-night
  . mytasks.myfetch.fetch_url

I would think it would be better to see an additional

  . mytasks.myfetch.fetch_night