_shepherd_tec_task_logs’ doesn’t exist errors

Resolved IanTh
(@ianth)

7 months ago

I have 12 different sites using TEC free version, all are now creating long error messages in the site error_logs – one or two each day, as per samples below. All sites are using versions 6.15.4, 6.15.5 or 6.15.6

Not new installs, these have been installed and running OK for several years.

[07-Oct-2025 03:01:03 UTC] WordPress database error Table ‘[database name].wpce_shepherd_tec_task_logs’ doesn’t exist for query DELETE FROM wpce_shepherd_tec_task_logs WHERE task_id IN (31) made by do_action_ref_array(‘action_scheduler_run_queue’), WP_Hook->do_action, WP_Hook->apply_filters, ActionScheduler_QueueRunner->run, ActionScheduler_Abstract_QueueRunner->run_cleanup, ActionScheduler_QueueCleaner->clean, ActionScheduler_QueueCleaner->delete_old_actions, ActionScheduler_QueueCleaner->clean_actions, ActionScheduler_QueueCleaner->delete_actions, ActionScheduler_DBStore->delete_action, do_action(‘action_scheduler_deleted_action’), WP_Hook->do_action, WP_Hook->apply_filters, TEC\Common\StellarWP\Shepherd\Provider->delete_tasks_on_action_deletion, TEC\Common\StellarWP\DB\DB::__callStatic, TEC\Common\StellarWP\DB\DB::runQueryWithErrorChecking, TEC\Common\StellarWP\DB\DB::TEC\Common\StellarWP\DB{closure}, call_user_func_array

[06-Oct-2025 12:43:21 UTC] WordPress database error Table ‘[database name].wpce_shepherd_tec_task_logs’ doesn’t exist for query DELETE FROM wpce_shepherd_tec_task_logs WHERE task_id IN (30) made by do_action_ref_array(‘action_scheduler_run_queue’), WP_Hook->do_action, WP_Hook->apply_filters, ActionScheduler_QueueRunner->run, ActionScheduler_Abstract_QueueRunner->run_cleanup, ActionScheduler_QueueCleaner->clean, ActionScheduler_QueueCleaner->delete_old_actions, ActionScheduler_QueueCleaner->clean_actions, ActionScheduler_QueueCleaner->delete_actions, ActionScheduler_DBStore->delete_action, do_action(‘action_scheduler_deleted_action’), WP_Hook->do_action, WP_Hook->apply_filters, TEC\Common\StellarWP\Shepherd\Provider->delete_tasks_on_action_deletion, TEC\Common\StellarWP\DB\DB::__callStatic, TEC\Common\StellarWP\DB\DB::runQueryWithErrorChecking, TEC\Common\StellarWP\DB\DB::TEC\Common\StellarWP\DB{closure}, call_user_func_array

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

Plugin Support tristan083
(@tristan083)

7 months ago

Hi @ianth ,

Thank you for bringing this to our attention.

Our products team are aware of this issue and currently working on addressing it.

We prioritize bugs by taking into consideration the number of users impacted as well as how the bug impacts one’s ability to run an event/sell tickets. I don’t have a specific timeline as to when this issue will be resolved, but trust that our team is aware. Our team communicates updates and bug fixes in our newsletter and via our changelog.

In the meantime, if this is affecting your ability to work with The Events Calendar, the recommendation is to downgrade to a prior version of the plugin (see Accessing and Installing Older Plugin Versions).

—

Internal Bug Ticket Reference: TCMN-200

Plugin Support Darian
(@d0153)

7 months ago

Hi there,

It looks like this thread has been inactive for a while, so I’ll go ahead and close it for now. Rest assured, we will update you through this thread once the fix is out.

If you have any other questions or concerns, please don’t hesitate to reopen this thread or start a new one.
Thread Starter IanTh
(@ianth)

6 months, 3 weeks ago
Some interesting further information that may help in debugging:

This error started on 12 sites on the same hosting platform, but the errors have one by one dried up and ceased! On each site, after 50 errors – where the IN (nn) part of the error message reached IN (50) – no futher error messages are generated, i.e. the last error message begins:

WordPress database error Table ‘<database>wp_shepherd_tec_task_logs’ doesn’t exist for query DELETE FROM wp_shepherd_tec_task_logs WHERE task_id IN (50) …
- This reply was modified 6 months, 3 weeks ago by IanTh.
Plugin Support Darian
(@d0153)

6 months, 3 weeks ago

Hi @ianth

Thank you for sharing this information. I’ve passed the details along to our team, rest assured, we’ll keep you updated as soon as a fix is available.

If you have any other questions or need further assistance in the meantime, please let us know—we’re here to help!

Plugin Support Darian
(@d0153)

6 months, 3 weeks ago

Hi there,

We haven’t heard back from you in a while, so I’ll close this thread for now. Rest assured, we’ll update you here as soon as a fix is available.

If you need further assistance, you’re welcome to reopen this thread or start a new one.

danielkoch
(@danielkoch)

6 months ago

@d0153: Why closing an issue without a solution? I have the same issue. What is the outcome of your investigation?

Plugin Support Darian
(@d0153)

6 months ago

My apologies for the delayed update. I wanted to let you know that we’ve created an internal bug ticket to address the issue mentioned above. I’ve linked this thread to that ticket, so you’ll automatically receive an update here once the fix is released.

@danielkoch I recommend opening a separate thread for your concern so we can provide more focused assistance. This also helps us comply with the WordPress Forum Guidelines.

Thank you all for your understanding and patience while our team works on resolving this.

—
Internal Bug Ticket Reference: TCMN-200

danielkoch
(@danielkoch)

6 months ago

@d0153: Thanks for your reply. Not quite sure why to open an new thread for the same topic.

I think I have the same issue and thought a thread will only be closed once a fix for a issue is available…

Plugin Support Darian
(@d0153)

5 months, 4 weeks ago

Hi @danielkoch

Thanks for your response. The best way to explain why each user should open a separate thread — even if they’re experiencing a similar issue — is by checking the official WordPress guidelines here:

🔗 I have the same problem. Can I just reply to someone else’s post with “Me too”?

Plugin Support tristan083
(@tristan083)

5 months, 3 weeks ago

HI @ianth ,

Checking in on the Shepherd issue you reported. We’ve shipped improvements related to this in a recent release and would appreciate hearing whether the issue is now resolved or has improved on your end. We really appreciate your patience while we work on these refinements.

The latest update to The Events Calendar includes an updated Shepherd library intended to address problems present in the older version. If you still run into any issues, just let us know and we’ll be happy to review the current behavior and respond in a time sensitive manner. https://theeventscalendar.com/release-notes/the-events-calendar/the-events-calendar-6-15-12/

As always, please test updates on a staging site first before applying them to your live site.

touchwood14
(@touchwood14)

5 months, 3 weeks ago

HI Support, this issue is happening on my installation. The action schedule logs fill uo to the extent that the webpage hardly functions

Plugin Support Darian
(@d0153)

5 months, 2 weeks ago

Hi @touchwood14

Thank you for reaching out. I understand this issue is impacting your website, and I apologize for the difficulty you are experiencing.

If you haven’t tried it yet, please check this workaround and see if this works on your end: https://ww.wp.xz.cn/support/topic/out-of-memory-28/#post-18697090

If the issue persists after attempting this step, please submit a new support thread. This ensures your specific case is tracked and addressed properly.

Thread Starter IanTh
(@ianth)

5 months, 1 week ago

Just to say that I have not seen any of the reported errors since updating to 6.15.12

(Bearing in mind that all my errors stopped after the 50th error in any case)

Thanks!

Plugin Support Darian
(@d0153)

5 months ago

Hi @ianth

I’m glad to hear the issue is now resolved! Just a quick reminder to make sure you’re using the latest version of our plugin (v6.15.12.2) so all recent fixes and patches are applied.

If you need anything else, feel free to let us know.

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

You must be logged in to reply to this topic.