<p>I had a similar issue where some queues would only run when I logged in via the control panel. The root cause is usually stalled or failed tasks, but I was able to get webhook tasks to run instantly by installing the <a href="https://plugins.craftcms.com/async-queue" rel="nofollow noreferrer">AsyncQueue plugin</a>.</p>

<p>From their <a href="https://github.com/ostark/craft-async-queue/blob/master/README.md" rel="nofollow noreferrer">docs</a>:</p>

<blockquote>
  <p>This plugin replaces Craft's default queue handler and moves queue execution to a non-blocking background process. The command craft queue/run gets executed right after you push a Job to the queue.</p>
</blockquote>

CC BY-SA 4.0
2019-02-03T13:25:28.107Z
Thanks for the heads up Stephen. After a little fighting to get the AsyncQueue plugin installed this seems to do the trick.
Dr_Codswallop
CC BY-SA 4.0
2019-01-26T15:24:01.180Z
2019-01-26T15:24:01.180Z
Stephen Bowling
<p>As my first delve into webhooks I've just installed the Pixel&amp;Tonic Webhooks plugin. I'm trying to send data from a front end contact form to Zapier. The front end form uses the Pixel&amp;Tonic Contact Form plugin and the webhook setting is set to the <code>beforeSend</code> event.</p>

<p>I've got the connections working although the webhook doesn't seem to fire automatically. It only sends data to Zapier when I refresh the admin control panel (a 'Sending webhook ...' task displays briefly at the bottom of the control panel's left sidebar). </p>

<p>The email is sending just fine and is immediately received, it's just the webhook that seems to be getting 'stuck'. Is there anything I'm doing wrong?</p>

<p><a href="https://i.sstatic.net/ol9LZ.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/ol9LZ.png" alt="Webhooks settings"></a></p>

<p><a href="https://i.sstatic.net/Ptjbb.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/Ptjbb.png" alt="Queue db table with stuck task"></a></p>

CC BY-SA 4.0
2019-01-10T20:09:40.183Z
Check your Craft log files for any clues? Is a job stuck in Craft's queue? The plugin pushes webhooks into the queue so if a job is stalled there, nothing else will go through.  Your settings look correct, FWIW.
Brad Bell
CC BY-SA 4.0
2019-01-11T00:55:57.677Z
I've cleaned out the `storage/logs` folder and retested a few times but nothing new showing up there. Nothing in the Apache error log either. I've also tried upping the PHP `max_execution_time` from 30 to 300 but that had no effect. Nothing in the `queue` db table other than the stuck webhook task _just added to original post_.
Dr_Codswallop
CC BY-SA 4.0
2019-01-13T16:22:45.827Z
Seeing some things come up in `queue.log` which related to the Olivemenus plugin I was using. I've uninstalled Olivemenus now. Webhook still hangs in the queue db table after form submission. After it fires on CP control panel login it clears out the queue db table and updates `queue.log` file with `2019-01-13 16:13:44 [-][1][-][info][craft\queue\QueueLogBehavior::beforeExec]  [329] Sending webhook “Email ➡️ Zapier” (attempt: 1) - Started
2019-01-13 16:13:44 [-][1][-][info][craft\queue\QueueLogBehavior::afterExec]  [329] Sending webhook “Email ➡️ Zapier” (attempt: 1) - Done (time: 0.370s)`
Dr_Codswallop
<craft3><plugins><plugin-contactform><tasks><hook>
Webhook plugin & hooking into Contact Form
# Webhook plugin & hooking into Contact Form

(Asked by: username_0 on 2019-01-10)

As my first delve into webhooks I've just installed the Pixel&Tonic Webhooks plugin. I'm trying to send data from a front end contact form to Zapier. The front end form uses the Pixel&Tonic Contact Form plugin and the webhook setting is set to the `beforeSend` event.

I've got the connections working although the webhook doesn't seem to fire automatically. It only sends data to Zapier when I refresh the admin control panel (a 'Sending webhook ...' task displays briefly at the bottom of the control panel's left sidebar).

The email is sending just fine and is immediately received, it's just the webhook that seems to be getting 'stuck'. Is there anything I'm doing wrong?

[![Webhooks settings](https://i.sstatic.net/ol9LZ.png)](https://i.sstatic.net/ol9LZ.png)

[![Queue db table with stuck task](https://i.sstatic.net/Ptjbb.png)](https://i.sstatic.net/Ptjbb.png)

**Tags:** craft3, plugins, plugin-contactform, tasks, hook

> **Comments:**
> **username_1**: Check your Craft log files for any clues? Is a job stuck in Craft's queue? The plugin pushes webhooks into the queue so if a job is stalled there, nothing else will go through.  Your settings look correct, FWIW.  
> **username_0**: I've cleaned out the `storage/logs` folder and retested a few times but nothing new showing up there. Nothing in the Apache error log either. I've also tried upping the PHP `max_execution_time` from 30 to 300 but that had no effect. Nothing in the `queue` db table other than the stuck webhook task _just added to original post_.  
> **username_0**: Seeing some things come up in `queue.log` which related to the Olivemenus plugin I was using. I've uninstalled Olivemenus now. Webhook still hangs in the queue db table after form submission. After it fires on CP control panel login it clears out the queue db table and updates `queue.log` file with `2019-01-13 16:13:44 [-][1][-][info][craft\queue\QueueLogBehavior::beforeExec]  [329] Sending webhook “Email ➡️ Zapier” (attempt: 1) - Started 2019-01-13 16:13:44 [-][1][-][info][craft\queue\QueueLogBehavior::afterExec]  [329] Sending webhook “Email ➡️ Zapier” (attempt: 1) - Done (time: 0.370s)`  

---

## 1 answers

### Answer by username_2 on 2019-01-26. Score: 1 | Accepted answer

I had a similar issue where some queues would only run when I logged in via the control panel. The root cause is usually stalled or failed tasks, but I was able to get webhook tasks to run instantly by installing the [AsyncQueue plugin](https://plugins.craftcms.com/async-queue).

From their [docs](https://github.com/ostark/craft-async-queue/blob/master/README.md):

> This plugin replaces Craft's default queue handler and moves queue execution to a non-blocking background process. The command craft queue/run gets executed right after you push a Job to the queue.

> **Comments:**
> **username_0**: Thanks for the heads up Stephen. After a little fighting to get the AsyncQueue plugin installed this seems to do the trick.  

---

