<p>If you set <a href="https://docs.craftcms.com/v3/config/config-settings.html#runqueueautomatically" rel="nofollow noreferrer">runQueueAutomatically</a> to <code>false</code> in your <code>config/general.php</code> file, that will disable that behavior.</p>

CC BY-SA 4.0
2020-06-02T14:40:28.317Z
Brad, how is this done in a plugin that returns data? (without setting the runQueueAutomatically to false in the global Craft instance) . I had a custom module pre-3.4 that now returns the queue runner script after its return data.
jpea
CC BY-SA 4.0
2020-09-30T21:56:58.890Z
The documentation states that it would only inject this in control panel requests, but I see these calls injected into my frontend sites (which, I would like to disable).
jishi
CC BY-SA 4.0
2020-05-20T21:02:03.083Z
2020-05-20T21:02:03.083Z
Brad Bell
<p>After upgraded our Craft from 3.3 to 3.4.14 we have noticed that there is a new Javascript on the footer of the homepage (frontend) that runs "index.php?p=actions/queue/run".</p>

<p>We run the tasks via crontab and there is no need for that. </p>

<p>How can we disable it on the frontend?</p>

<p>Thank you</p>

<craft3>
How to disable the Javascript "actions/queue/run" on frontend?
# How to disable the Javascript "actions/queue/run" on frontend?

(Asked by: username_0 on 2020-05-20)

After upgraded our Craft from 3.3 to 3.4.14 we have noticed that there is a new Javascript on the footer of the homepage (frontend) that runs "index.php?p=actions/queue/run".

We run the tasks via crontab and there is no need for that.

How can we disable it on the frontend?

Thank you

**Tags:** craft3


---

## 1 answers

### Answer by username_1 on 2020-05-20. Score: 2

If you set [runQueueAutomatically](https://docs.craftcms.com/v3/config/config-settings.html#runqueueautomatically) to `false` in your `config/general.php` file, that will disable that behavior.

> **Comments:**
> **username_2**: Brad, how is this done in a plugin that returns data? (without setting the runQueueAutomatically to false in the global Craft instance) . I had a custom module pre-3.4 that now returns the queue runner script after its return data.  
> **username_3**: The documentation states that it would only inject this in control panel requests, but I see these calls injected into my frontend sites (which, I would like to disable).  

---

