<p>This happened to me also.</p>
<p>I think this only happens when you are in Dev mode.</p>
<p>Once in production the queues just worked.</p>

CC BY-SA 4.0
2024-03-05T11:34:07.317Z
Thanks! This worked. I had to set DEV_MODE=false and CRAFT_ENVIRONMENT=production
Graham Bennett
CC BY-SA 4.0
2024-02-29T22:07:45.457Z
2024-02-29T22:07:45.457Z
Stu00
<p>You'll want to setup a cron job, daemon, or other solution as all versions of Craft CMS can only fire the queue when the admin panel is logged into (HTTP). Please check out:</p>
<p><a href="https://craftcms.com/docs/4.x/queue.html#queue-runners" rel="nofollow noreferrer">https://craftcms.com/docs/4.x/queue.html#queue-runners</a></p>
<p>and this handy article by NYStudio107</p>
<p><a href="https://nystudio107.com/blog/robust-queue-job-handling-in-craft-cms" rel="nofollow noreferrer">https://nystudio107.com/blog/robust-queue-job-handling-in-craft-cms</a></p>

CC BY-SA 4.0
2024-03-05T11:31:15.050Z
Thank you I'll try this.
Graham Bennett
CC BY-SA 4.0
2024-03-03T01:16:16.383Z
2024-03-03T01:16:16.383Z
cherrykoda
<p>I've set up a Webhook in Craft 4 that triggers a Zap.
The Sender class is craft\commerce\elements\Subscription and the event name is afterSave.
When the trigger action happens (a user subscription), the Webhook does not fire until I log in to the Craft CP, even if I wait a couple of hours. It is listed as status &quot;pending&quot;, then when I refresh the page, it's listed as status 200, and the Zap is activated and works fine.</p>
<p>How can I make it fire automatically? (I'm assuming that is the intended behaviour)</p>
<p>Thanks</p>

<plugin-craftcommerce><craft4><plugin-webhooks>
Webhook only firing when I log in
# Webhook only firing when I log in

(Asked by: username_0 on 2024-02-28)

I've set up a Webhook in Craft 4 that triggers a Zap.
The Sender class is craft\commerce\elements\Subscription and the event name is afterSave.
When the trigger action happens (a user subscription), the Webhook does not fire until I log in to the Craft CP, even if I wait a couple of hours. It is listed as status "pending", then when I refresh the page, it's listed as status 200, and the Zap is activated and works fine.

How can I make it fire automatically? (I'm assuming that is the intended behaviour)

Thanks

**Tags:** plugin-craftcommerce, craft4, plugin-webhooks

---

## 2 answers

### Answer by username_1 on 2024-02-29. Score: 1 | Accepted answer

This happened to me also.

I think this only happens when you are in Dev mode.

Once in production the queues just worked.

> **Comments:**
> **username_0**: Thanks! This worked. I had to set DEV_MODE=false and CRAFT_ENVIRONMENT=production  

---

### Answer by username_2 on 2024-03-03. Score: 1

You'll want to setup a cron job, daemon, or other solution as all versions of Craft CMS can only fire the queue when the admin panel is logged into (HTTP). Please check out:

<https://craftcms.com/docs/4.x/queue.html#queue-runners>

and this handy article by NYStudio107

<https://nystudio107.com/blog/robust-queue-job-handling-in-craft-cms>

> **Comments:**
> **username_0**: Thank you I'll try this.  

---

