Investigate overdue WooCommerce, email, backup or automation actions without deleting the queue blindly.
Applies to: WordPress on Tudor Internet Web Hosting
WordPress problems often come from the interaction between PHP, plugins, themes, caching, scheduled tasks and database state. Change one item at a time, record what you changed and keep a known-good backup before updates or repairs.
Before you start
- Sign in to the Customer Portal and open the affected hosting service.
- Take a current backup before changing website files, databases, DNS or application configuration.
Work through these checks
- Identify the queue system and list overdue, failed and pending actions with their hook names and scheduled times.
- Check whether wp-cron runs and whether the account recently hit CPU, memory, entry-process or storage limits.
- Open the first failed action and record the exception or callback error before retrying it.
- Correct the underlying plugin, database, remote API or credential problem before running a large backlog.
- Process a small batch and monitor PHP, database and resource use to avoid making the website unavailable.
- Remove only actions confirmed to be obsolete; recurring actions may be recreated immediately by their plugin.
- Confirm new actions complete at the expected rate and set monitoring for another growing backlog.
Confirm the result
- The intended hostname loads over HTTPS from a private browser session and serves the correct website.
- Forms, database-driven pages and the administration area work without a new PHP, permission or redirect error.
Common problems
| Symptom | Likely cause | What to do |
|---|---|---|
| The problem started immediately after a change. | A deployment, plugin, permission, PHP or configuration change introduced the fault. | Roll back only the last known change, clear caches and retest before making a second change. |
| The fault is intermittent. | Resource limits, traffic spikes, remote dependencies or scheduled work may be involved. | Record exact timestamps and compare them with CloudLinux usage, application logs and the Service Status page. |
When to contact Tudor Internet
Open a ticket through the Customer Portal when the checks above do not resolve the issue, when an action is unavailable for your service, or when continuing could risk data loss or service interruption. Include the following so the request can be investigated efficiently:
- The affected domain and SiteWorx account
- The exact error text and time
- The last change made
- Relevant log lines with passwords and personal data removed
Do not send passwords, private keys, full payment-card details, one-time authentication codes or unredacted identity documents in an ordinary support reply.
Related articles
- Configure WordPress scheduled tasks and wp-cron
- Resource limit errors and slow sites
- View website and error logs
- Find database connection details
- Configure and clear WordPress caching safely
Last reviewed: 2026-07-18.
