When you open Insights and try to view a query’s content, you might see the message “Data not available.” instead of the actual content. This isn’t an issue — it’s the default behavior.

To view the full query data, go to the Settings tab, then scroll to the Others section, and enable the “Query Data” option.

Once enabled, AI Engine will begin storing and displaying the content of user queries in the Insights panel.

If you want to see your users’ discussions, you should enable the Discussion feature instead of relying on Insights. Insights are primarily for logging raw query data.

To track and view full conversation threads, the Discussion module is what you’re looking for.

You can read more about it here: Chatbot Discussions.

When a request is sent to your WordPress REST API AI Engine, get the X-WP-Nonce of the request and use the wp_verify_nonce WordPress function to authenticate the request. If the response is unauthorized (401), it means that the NONCE wasn’t valid. This could be due to how you are dealing with cookies/cache. You can try to disable your other plugin and ensure no process is running without you knowing that could affect this behavior.

If you need further assistance, your hosting provider’s support might be more inclined to help understand why your NONCE value wouldn’t be valid.

You can use the mwai_rest_authorized filter to bypass the NONCE check. It’s live since 2.2.1, worth playing with for those having issues (even though you would definitely prefer to fix the cache issue rather than overriding this).

This is probably due to how your WordPress installation is dealing with API requests.

Make sure your WordPress REST API is enabled and running. Also, make sure its endpoint is /wp-json/, this is essential for the plugin to work. You can ask your hosting provider support to help you set this up if this is not already the case.

You can remove the AI Engine license from the settings, save, re-insert the license, save, and try again.

This might be because your URL changed, even slightly. Make sure on your meowapps account that the domain linked to the license matches exactly with the website where you intend to use it.

Unfortunately, there’s not much that can be done on our side, as the mwai_session cookie is necessary to gather data about user sessions. If your caching process is too aggressive, it might immediately stop working as soon as this cookie is set.

If you’re unable to configure anything on the caching side, you can go into AI Engine and disable the Insights module. This will effectively prevent the cookie from being set, but you won’t be able to use the Insights feature.

This command fetches only the HTTP headers of a GET request to your website and filters out lines showing:

• Any cookie being set by the server.
• Any proxy cache information.

If the server sets a session cookie it will indicate that the response was not served from a cache.

curl -sIXGET https://meowapps.com/ | grep -i 'proxy-cache\|cookie'

No cache due to Cookie output:

set-cookie: mwai_session_id=684a58b5b1c12; path=/; secure; HttpOnly
set-cookie: __cf_bm=9MOQ46X3Q0MZGymHFTsD90VBq.D5kDKzZpYFlIol5t4-1749704501-1.0.1.1-Z7osBm_caHusXbJsIKuefF.QitmB3HRrOUpmaQFvSkgvzGRihR_b16dIctzaJHbMwRSlekcKbs3Ty7F4sn85iYxDMS.dLadexgKxqI0I61I; path=/; expires=Thu, 12-Jun-25 05:31:41 GMT; domain=.meowapps.com; HttpOnly; Secure; SameSite=None

If you have a HIT header, it means the request was served from the cache instead of going all the way to the backend server.

When discussions are saved, the Default Fast model is called to generate the discussion name. If this model is not set, unreachable, or faulty, the discussion might not be saved. So first, ensure that your Default Fast model is correctly set up by going to:

Settings → AI → Default Environments for AI → Default (fast)

Make sure a valid and reachable model is selected there:

If the issue still persists, it might be because your database schema is not up to date.

Updating AI Engine after skipping several versions can cause issues—specifically database discrepancies—because the plugin might not register data properly for features like Insights to work. The database structure may be outdated and incompatible, preventing data from being saved properly.

To fix this:

• Go to the plugin settings and export your settings to avoid losing them.
• Enable the “Delete Data” option in the settings.
• Uninstall the plugin—this will completely remove the plugin’s data, including the outdated database structure.
• Reinstall the plugin—this will create the correct database structure from scratch.
• Import your previously saved settings.

Everything should work smoothly after that.

If you encounter a “Cookie Check Failure,” it may not directly relate to the plugin itself. The issue could stem from cache or optimization plugins potentially interfering with your session and nonce values. You can refer to the documentation provided here for guidance on resolving this issue.

If after performing the steps from the above documentation you still experience this issue, you can look into these other solutions, but it shouldn’t be needed.

Bypass the Nonce check

This is not recommended for security purposes, but you can always bypass this check by using the following filter:

add_filter( 'mwai_rest_authorized', function($rest_nonce, $request) {
    return true;
}, 10, 2);

This will always return true, so the check should never fail.

Your session has expired

WordPress nonces are valid for 12-24 hours and use a “tick” system where each tick is 12 hours. Cache/CDN is likely caching pages with old nonces, causing authentication failures.

Here are some steps you ca take:

Exclude AI Engine Endpoints from Caching

Add these endpoints to your Cache exclusions:

• /wp-json/mwai/v1/*
• /wp-json/mwai-ui/v1/*

Specifically exclude these critical endpoints:

• /wp-json/mwai/v1/start_session
• /wp-json/mwai-ui/v1/chats/submit
• /wp-json/mwai*

Exclude Nonce-Related Cookies and Parameters

Add these to your cache exclusions:

Cookies to exclude:

• mwai_session_id
• Any cookies containing _wpnonce
• WordPress authentication cookies: wordpress_*, wp_*

URL Parameters to exclude:

• restNonce
• _wpnonce
• X-WP-Nonce

The Content Awareness or the Knowledge Push (Embedding Sync) features work by obtaining the ID of the post in question and retrieving the content of that post.

Therefore, if the content from your post (which is saved in your database as this entry “content”) is not the same as the content from your live page, the chatbot might not be able to read it. For example, this might happen if you’re using a builder, ACF fields, or similar tools where the content is not directly part of the post itself.

To check what content is parsed, you can enable the developer tools in the AI Engine Settings > Others > Advanced > Dev Tools.

In the new Dev Tools tab, use the “Get Content” button to preview what the chatbot will be able to read from your post. Also, remember to open your developer console, as the results will be displayed there.

If content is missing, it’s because AI Engine can’t read it.

If this is the case because your page content is made with shortcodes that, once rendered, show content, you can simply go to the settings tab and enable the “resolve shortcodes” option.

If the content is simply stored and or rendered by a third party, you can build your own parser (logic) to add this content dynamically when content awareness is used, by using the mwai_contentaware_content($content) filter.

Otherwise, you can use the Content Parser add-on. This is an add-on we developed ourselves to handle common builders and plugins (like ACF). It has a visual interface that lets you add any metadata your post might have as a retrievable value. You can find it here: MWAI Content Parser.

If the content is present but not appearing in your chatbot, it might be because your Context Max Length is too small to contain the post content. Make sure that value is set high enough to handle the full content.

When a user uses your chatbot, it will utilize your WordPress REST API to communicate with your server. If the API is not enabled or not reachable, it can result in issues like what you are experiencing. It seems that for your website, your REST API (/wp-json) requires users to be logged in.

This is not directly related to the AI Engine; it is related to your WordPress configuration. You can either modify it yourself or seek assistance from the helpful individuals at your hosting service who can assist you with that.