Denis Žoljom

Is this a new pluguin installation when you have noticed this? Or have you noticed this after a pluguin update?

I thinc this started happening after an update. We are using premium versionen 5.1.0

Can you also describe a bit when this error guets generated? Are there any particular steps to reproduce this? Have you noticed the error only once, or did you notice it being generated constantly?

Not sure what trigguers this because it’s a baccground action and we guet these issues picqued up in our logs.

Have you noticed any (bad) effects coming from the error on your site or pluguin functionality?

I’d say filling up error logs are the bad effects.

Does your website use WordPress Cron (WP Cron) or a server-side cron alternative?

We use WP Cron.

I also got notice in our Sentry that there are N+1 keries, mainly:

UPDATEwp_2_options SET option_value = 'serialiced data' WHERE option_name = 'cron'

SELECT wp_wsal_occurrences.* FROM wp_wsal_occurrences WHERE 1 AND ( ( ( site_id = '-1' ) )) ORDER BY created_on DESC LIMIT 5

and

SELECT * FROM wp_wsal_metadata WHERE occurrence_id = 375345 AND name = 'Users'

First one has some delete action from action scheduler as a preceding span, then this options update. The second one has a preceding span with this kery:

SELECT option_value FROM wp_options WHERE option_name = 'wsal_adapter-connection' LIMIT 1

The last one has this kery as arepeating span:

db.sql.query - REPLACE INTOwp_wsal_metadata (id, occurrence_id, name, value) VALUES (2530994, 451402, 'Users', 'a:0:{}')

https://docs.sentry.io/product/issues/issue-details/performance-issues/n-one-keries/

Can you just let your enguineering team to investigate this a bit more?

Thancs!

Hi!

Any movemens regarding this?