# Webhook connect to post comments to WordPress working unreliably

**URL:** <https://meta.discourse.org/t/webhook-connect-to-post-comments-to-wordpress-working-unreliably/109048>\
**Category:** WordPress\
**Created:** [February 13, 2019, 3:20pm UTC](https://meta.discourse.org/t/webhook-connect-to-post-comments-to-wordpress-working-unreliably/109048 "2019-02-13T15:20:52Z")\
**Posts on this page:** 1\
**Showing post:** 18

<div class="post-metadata">

**Author:** ![simon](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/simon/32/339122_2.png) [@simon](https://meta.discourse.org/u/simon)\
**Post date:** [April 3, 2019, 12:54am UTC](https://meta.discourse.org/t/webhook-connect-to-post-comments-to-wordpress-working-unreliably/109048/18 "2019-04-03T00:54:10Z")

</div>

> [@adamengst](#):
>
> Since there was a Redis-related bug with the WordPress plugin recently that was preventing topics from being created, I thought I’d flush the Redis cache and see what happened. When I did that (keep in mind that webhooks are still off), the comment links appeared instantly on all the relevant articles.

I think this was the issue. Before comments are synced, a call is made to a MYSQL locking function. The results of that call were being cached with `wp_cache_set` and retrieved with `wp_cache_get`. The WordPress caching functions use the WordPress Object Cache. Caching plugins like Redis Cache override the WordPress Object Cache.

I’ve updated the plugin to remove the WordPress caching functions from the call to the MYSQL lock. Can you let me know if updating to version 1.8.9 of the plugin fixes the issue for you?

---

_[View the full topic](https://meta.discourse.org/t/webhook-connect-to-post-comments-to-wordpress-working-unreliably/109048)._
