Check System Status
Check the health of your REST connection, background jobs, email, AI and storage.
On this page
Overview
System Status lives under Settings → System → System at #/settings/system/system. It reports queue depth, cron last run, REST namespace elegant-support/v1, rewrite/permalink health, email/IMAP, AI, schema, storage, feature flags, and diagnostics. The same panel holds Restart onboarding, queue_batch_size, and remove_data_on_uninstall (off by default).
When to use this
Use System Status to distinguish configuration, dependency, background-job, and permission problems before changing unrelated settings.
Where to find the controls
#/settings/system/system. Settings Overview also shows a System status side card. WordPress Site Health is complementary.
Who can make these changes
manage_settings. Hosting staff may need SSH for PHP extensions.
Before you begin
Run the listed health tests (rest, queue, cron, email, ai, schema, storage). Enable IMAP on the host if inbound is required. Set uninstall wipe only if you intend to DROP wp_helsup_support_* tables and delete es_* options when the plugin is deleted.
Follow these steps
- Open System Status.
- Read failed chips.
- Flush permalinks on REST 404.
- Fix IMAP/cron/AI as labeled.
- Re-run tests.
- Only then file a support request.
Settings reference
Health rows with state enabled / unavailable_requirement / unavailable_license / disabled. queue_batch_size. remove_data_on_uninstall. Restart onboarding. Diagnostic test buttons.
Example workflow
Email test shows IMAP unavailable. You install php-imap, reload Status, enable inbound, and the next cron poll creates tickets.
Good practices
Screenshot Status (no secrets) before contacting support. After plugin updates, hard-refresh and re-run REST/schema tests.
Important considerations
Uninstall: follow WordPress plugin deletion. If remove_data_on_uninstall is off, tables and options remain. If on, uninstall.php drops wp_helsup_support_* tables, deletes es_* options and transients, and user meta es_preferences. Export tickets first either way.
If something does not work
All tests fail: bootstrap/REST 401 — log in again, exclude caches. Schema fail after update: follow the plugin updater, do not edit tables by hand. Contact support with test names and states.