Setting RQ_ASYNC = False doesn't affect scheduling · Issue #22 · rq/Flask-RQ2 · GitHub
Skip to content

Setting RQ_ASYNC = False doesn't affect scheduling #22

Open
Open
Setting RQ_ASYNC = False doesn't affect scheduling#22

Description

@JanChec
JanChec
opened on May 15, 2017

Hey,

in my tests I use RQ_ASYNC = False which works fine for .queue(), but seems to do nothing for .schedule().

Thank you in advance!

Activity

  1. jezdez commented on Dec 4, 2017

    @jezdez
    jezdez
    on Dec 4, 2017
    Contributor

    Hmm, this isn't a feature that is included in rq-scheduler, so I'm not sure if this is something Flask-RQ2 should add on top. Could you elaborate what type of behavior you expect? As soon as a job is scheduled, it should be run? How would that work for jobs that are scheduled on module level with rq.schedule(...) instead of inline of a (view) function?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions