Diagnose common WordPress, licensing, provider, cron and cache failures
Use an administrator account, make a current backup before structural changes, and never paste passwords or complete API or licence keys into screenshots or support requests.
What this guide covers
- Where to find every control used in this workflow
- What each setting changes and when to use it
- How to verify the result before relying on it in production
- What evidence to collect if the result differs from the expected behaviour
1. Classify the failure
Determine whether the issue is account/licence, connection, data/indexing, background processing, presentation or a third-party dependency.
Procedure
- Write one sentence describing expected and actual behaviour.
- Reproduce it once.
- Note the first exact error and timestamp.
- Do not change several settings simultaneously.
The problem has one testable category.
2. Check the environment
Most false diagnoses come from version, cache, cron or outbound-request differences.
Procedure
- Check Site Health and product diagnostics.
- Confirm HTTPS and correct site URL.
- Clear all cache layers.
- Verify WP-Cron or Action Scheduler.
- Test provider status/billing and server outbound requests.
The environment can execute the intended workflow.
3. Isolate safely
Use staging and reversible changes.
Procedure
- Temporarily disable only a suspected conflicting optimisation.
- Retest with a default browser session.
- Inspect logs around the timestamp.
- Restore the original setting after the comparison.
Evidence identifies or excludes a component.
Final verification
- Save the configuration and reload the screen to confirm it persisted.
- Test in a private browser session so administrator state and old cookies do not hide the real visitor experience.
- Test one normal case, one boundary case and one deliberate failure.
- Review the relevant product log, job, report or diagnostic screen.
- Record the installed product, WordPress, PHP and WooCommerce versions with the test result.
Troubleshooting checklist
- Confirm the licence is active for this exact product and environment.
- Check provider access, billing and model availability.
- Clear every active cache layer after settings or content changes.
- Verify background processing and inspect the first error, not only the final symptom.
When to contact support
Contact support only after repeating the test with caches cleared and current versions. Include exact steps, expected and actual results, the safe error text and a diagnostic export when available. Mask licence and API keys; do not send customer personal data.