Diagnostics answers the question every support reply starts with: what is actually running on this site? It performs no actions and changes nothing. It reads, formats and shows.
Environment:
WordPress, PHP and MySQL versions, the Hub version, the catalogue version, your site and admin addresses, the active theme and its parent if it is a child theme, whether the install is multisite, whether WP_DEBUG and the debug log are on, the server software, and the four limits that break things most often: memory limit, maximum execution time, upload maximum and post maximum.
Registered ResultsAiX plugins:
Every plugin that has registered with the Hub, with its slug, name, version, whether it is a parent or an add on, and its plugin file. An update label appears next to any version with a newer release waiting.
All active plugins:
Every plugin active on the site, other makers' plugins included, with version, author and plugin file. Rows are tagged so the three groups are obvious: RAIX for plugins registered with the Hub, RAIX (pre-hub) for ResultsAiX plugins without a registration block yet, and no tag for everything else. This section is the one that solves plugin conflicts, which is why it lists everything rather than only ResultsAiX plugins. Inactive plugins are counted but not listed.
Must use and drop in plugins:
If the site has any, they get their own table. These are files WordPress loads on its own, from wp-content/mu-plugins (must use) or straight from wp-content (drop ins). Your host or another plugin usually puts them there, and they cannot be switched off from the Plugins screen. Most are harmless. Each one gets a plain English line saying what it does, for example:
- maintenance.php: your own back in a minute page, shown for a few seconds while WordPress installs updates
- advanced-cache.php: page caching from a caching plugin or your host. If a change does not show on the site, clear the cache
- object-cache.php: database caching, added by your host or a caching plugin
- db.php: replaces how WordPress talks to its database, added by some hosts, caching and security plugins
The list is there so support can spot a conflict quickly. You do not need to do anything about it.
Database and cron:
The two Hub tables are checked for existence and row count, with a clear Missing marker if either is absent. The cron section shows when the daily refresh is next due, in UTC and as a countdown. If it says it is not scheduled, it should schedule itself on the next admin page load; if it never does, check that WordPress's scheduled tasks (WP-Cron) are running on your site.
The diagnostic report:
At the bottom is a plain text version of everything above in one box, with a Copy report button that copies it in one click and confirms. Paste that straight into your support ticket, and do not trim it: the full picture is what lets a problem get solved on the first reply rather than the fourth. The Open Support button next to it takes you to the Support tab.