Scheduled events returning errors
-
Hi! We got the following errors in our logs:
Cron reschedule event error for hook: wsal_generate_reports_cron, Error code: invalid_schedule, Error message: Event schedule does not exist., Data: {"schedule":"tenminutes","args":[],"interval":600}
Something is wrong with registering your custom time intervals.
-
Hello Denis!
I am really sorry to hear about this experience with our plugin! I would have a few questions for you, just to create some context around this:
1. Is this a new plugin installation when you have noticed this? Or have you noticed this after a plugin update?
2. Can you also confirm which plugin version are you using (latest is 5.2.1) ? Also, are you using the Free or Premium edition when noticing this?
3. Can you also describe a bit when this error gets generated? Are there any particular steps to reproduce this? Have you noticed the error only once, or did you notice it being generated constantly?
4. Have you noticed any (bad) effects coming from the error on your site or plugin functionality?
5. Does your website use WordPress Cron (WP Cron) or a server-side cron alternative?
Looking forward to hearing back from you on this.We are getting the same issue on 5.2.1 Free version. This cron seems to constantly run when this happens recreating a recurring task over and over within the Activity Log. Any ideas how to prevent this?
Hello rhinogroup!
I am really sorry to hear about this experience with our plugin! It seems indeed that might be related to the original ticket description error, so could you please answer a few questions as well:
- Can you confirm that you are also seeing the same errors collected in debug log as Denis mentioned above? If so, are there any specific steps that you have done in order to reproduce these constantly? If you can share this with us, it would really help a lot.
Example: Cron reschedule event error for hook: wsal_generate_reports_cron, Error code: invalid_schedule, Error message: Event schedule does not exist., Data: {“schedule”:”tenminutes”,”args”:[],”interval”:600} - Can you confirm the source of the image you shared with us so that we can understand how you discovered this?
- Can you please send us the system information file via email on [email protected] ? This file includes information about your website and our plugin’s setup so we can better understand how it is configured. You can get the system information file from the?System Info?tab in the?Help & Contact Us?section in the plugin.
IMPORTANT: as the file contains sensitive site information, please send it over to us via email as instructed on [email protected] while referencing this ticket.
4. Have you noticed any (bad) effects coming from the error on your site or plugin functionality?
5. Does your website use WordPress Cron (WP Cron) or a server-side cron alternative?
Looking forward to hearing back from you on this along with the answers to my questions. If there is any other sensitive data or information in your answers, feel free to share all the answers to my questions via email in order to avoid disclosing compromising data here on the forums.
Many thanksIs this a new plugin installation when you have noticed this? Or have you noticed this after a plugin update?
I think this started happening after an update. We are using premium version 5.1.0
?Can you also describe a bit when this error gets 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 triggers this because it’s a background action and we get these issues picked up in our logs.
Have you noticed any (bad) effects coming from the error on your site or plugin 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 queries, mainly:
UPDATE
wp_2_options
SEToption_value
= 'serialized data' WHEREoption_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 query:
SELECT option_value FROM wp_options WHERE option_name = 'wsal_adapter-connection' LIMIT 1
The last one has this query as arepeating span:
db.sql.query - REPLACE INTO
wp_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-queries/
Can you just let your engineering team to investigate this a bit more?
Thanks!
Hello again Denis!
Thank you so much for the elaborate response!
Since forums are reserved for Free users, can you please send us the system information file via email on?[email protected]?? This file includes information about your website and our plugin’s setup so we can better understand how it is configured. You can get the system information file from the?System Info?tab in the?Help & Contact Us?section in the plugin.
This will be helpful in troubleshooting the first issue related to the crons, and also to create some context.
Cron reschedule event error for hook: wsal_generate_reports_cron, Error code: invalid_schedule, Error message: Event schedule does not exist., Data: {“schedule”:”tenminutes”,”args”:[],”interval”:600}
Looking forward to hearing back from you on this via email along with the information provided! We shall then continue troubleshooting this.
Make sure you also reference this support ticket when sending us the email, so that we can correlate accordingly.
Many thanks!Hello again?rhinogroup!
The author of this support thread will be assisted via email since he is a Premium user, so I will also close this post.
You can open a separate thread here, on the forums, and provide us with all the answers to my previously addressed questions which will help in building a solid starting ground (please see list above on my previous reply towards you) and we will surely assist you with this as well moving forward.
Thank you for your understanding and looking forward to hearing back from you on this!- This reply was modified 3 weeks, 5 days ago by Lucian Padureanu.
We are seeing this error in our logs as well. We are on the free version.
Hello @claytonl
Thank you for using our plugin.
Even though you might be getting the same error, due to many other factors your issue might be caused by other circumstances. So to get support from us, please start your own forum thread.
Thank you for your cooperation and understanding.
- Can you confirm that you are also seeing the same errors collected in debug log as Denis mentioned above? If so, are there any specific steps that you have done in order to reproduce these constantly? If you can share this with us, it would really help a lot.
- You must be logged in to reply to this topic.