tplomari

@foosantos I’m a bit confused – if this is a new plugin, how do the support forum and reviews for it go back years and years? That doesn’t make sense.

Yes, WP Engine is killing the query – but it’s killing the query because there are SO many rows of these jpsq_sync options. I’ve had a nearly identical problem to the OP. The problem isn’t WP Engine…it’s that there are 1000’s (or in my case 174,000 across our multisite) of rows of data being added to our options table by Jetpack. Overriding WPE’s “Governor” doesn’t fix the actual problem…

Noooo! Have you tried disconnecting and reconnecting the Jetpack connection (not the plugin activation)?

@mindtakerminis – interesting, when I deactivated through the admin dashboard, reactivated, then reconnected Jetpack, the massive number of jpsq_sync rows in the options table went completely away….So far for the sites for which I’ve done this they’ve not returned. But the fun part is that I managed a multisite of almost 400 sites so manually doing this for each of them is NOT ideal…and I am really hoping to understand what caused it bc I don’t want to ever deal with this again. 174,000 rows of needless data across my dang multisite. C’mon now. Eesh. I’ll post back here if I figure out the source of it.

Update: it looks like there were up to 1,000 rows in wp_options with option_name containing jpsq_sync for the sites in which we received the above mentioned error. I’m still unsure of why that happened, but deactivating and reactivating cleared the massive number of rows of those options for now. Would love to know why this occurred to begin with! Thanks!

@whistlerdan Any update or resolution on this issue?

Similarly, I’m very confused as to why the thread about how long the Classic Widget will be maintained is locked. Seems like an important topic that we’d all like to stay up to date on?