Investigation
Investigating WordPress backend timeouts
The front end worked. The admin area did not. A visible error is the starting point, not a diagnosis.
The problem behind the job
If the WordPress admin times out while the front end appears normal, I treat it as an investigation rather than guessing which plugin, process or database issue is to blame.
What I was working with
My troubleshooting work has included WordPress backend timeouts, hosting issues and problems around WooCommerce or import workflows. In some cases the front end could still be reached while the admin task failed. That needed investigation of the affected workload, not an automatic full-site rebuild.
Find the operation that fails
The useful detail is often what was happening when the error appeared: opening an admin screen, processing an import or running background work.
The work records include 504 and backend issues, database scaling questions and import-plugin regressions.
Keep several possible causes open
Hosting limits, the amount of work being requested and plugin behaviour can all be relevant. I'd not infer the complete cause from the error number alone.
My work included investigating those areas and identifying workarounds in particular cases.
Describe investigation as investigation
Not every issue in the source history has a confirmed final fix. Some work established a workaround or narrowed the problem rather than closing the whole incident.
This page is an account of that diagnostic work, not a claim that every backend fault was permanently resolved.
What action causes the error on your site?
If your problem looks similar, send me the current setup and the outcome you need. The implementation may be different, but the same kind of thinking usually applies.
Test a specific change
For another site, I'd want a repeatable failing action, the relevant environment details and a safe way to test the change. A comparison is much more useful when the same task is tried before and after.
A defined acceptance test stops the job relying on 'it seems quicker'.
Look at connected workloads
A scheduled-action backlog or an import process may be relevant to the investigation, but neither should be blamed without checking.
See WordPress and WooCommerce work for the wider scope.
HAVE SOMETHING AWKWARD?
What action causes the error on your site?
Send me the URL, what is happening, what you have already tried and what a useful result would look like. A small anonymised sample is enough to start - do not send passwords, credentials or sensitive customer data.