Forum Replies Created

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter SaskiaMensink

    (@saskiamensink)

    Thank you shahzeen, this is very helpful.

    I have now shared these findings with the third-party fulfillment provider, including the successful webhook.site test and your suggestions about custom webhook handling, webhook scheduling, order status/hooks, and possible Mollie/iDEAL compatibility considerations.

    I will wait for their response first. If they come back with anything that points back to WooCommerce core or standard webhook behavior, I’ll update this topic.

    Kind regards,
    Saskia

    Thread Starter SaskiaMensink

    (@saskiamensink)

    Hi shahzeen, Thank you, this was very helpful.

    I created a separate WooCommerce order.created webhook using webhook.site as the delivery URL.

    Result:

    • WooCommerce created a woocommerce_deliver_webhook_async scheduled action.
    • The action completed successfully.
    • WooCommerce created a webhooks-delivery log.
    • Webhook.site received the request.
    • The response was 200 OK.

    So WooCommerce core, WP-Cron and Action Scheduler seem to be working correctly in general.

    This makes the issue look more specific to the third-party fulfillment webhook/plugin/endpoint, or to the way that webhook is registered or processed.

    For comparison:

    • The webhook.site test webhook has webhook_id 5 and created the scheduled action normally.
    • The third-party fulfillment order.created webhook is also active, but earlier real paid orders did not create a visible woocommerce_deliver_webhook scheduled action or delivery log for that webhook.

    Would the next logical step be to contact the third-party fulfillment provider and ask why their webhook/plugin does not appear to follow the same delivery flow, or is there still anything else I should check in WooCommerce first?

    Kind regards,
    Saskia

Viewing 2 replies - 1 through 2 (of 2 total)