Data Not Available

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.

You Don’t Have Permission To Do This

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).

Sorry, You Are Not Allowed To Do That

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.

Update Failed: Download Failed Unauthorized

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.

Permission Issues

Disabled Cache Issues

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.

Discussions / Queries not saving

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.

Cookie Check Failure

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.

AI Engine code change

This is not recommended, but it might be worth a try. You can change the clean_params function directly in AI Engine’s code and see if that helps you. Please note that this code will be erased every time you update the plugin. You can find this function in “chatbot.php” line 518.

function is_numeric_no_sci($value) {
    // Check if the value is numeric
    if (is_numeric($value)) {
        // Check if it's in scientific notation by looking for patterns like 1e10, 1E10, etc.
        if (preg_match('/[+-]?\\d*\\.?\\d+[eE][+-]?\\d+/', $value)) {
            return false; // It's numeric in scientific notation, so we don't accept it
        }
        return true; // It's numeric and not in scientific notation
    }
    return false; // It's not numeric at all
}

function clean_params( &$params ) {
    foreach ( $params as $param => $value ) {
        if ( empty( $value ) || is_array( $value ) ) {
            continue;
        }
        $lowerCaseValue = strtolower( $value );
        if ( $lowerCaseValue === 'true' || $lowerCaseValue === 'false' || is_bool( $value ) ) {
            $params[$param] = filter_var( $value, FILTER_VALIDATE_BOOLEAN );
        }
        else if ( $this->is_numeric_no_sci( $value ) ) {
            $params[$param] = filter_var( $value, FILTER_VALIDATE_FLOAT );
        }
    }
    return $params;
}

LiteSpeed Servers

If you are operating AI Engine on a LiteSpeed server (with ESI/User very turned on) and are using the latest server and plugin versions, you may be experiencing a higher frequency of Cookie Check Failures. After thorough exploration and discussions with LiteSpeed, it has been identified that a combination of factors has led to LiteSpeed NOT purging the wp_rest nonce, which AI Engine checks. This issue is expected to be addressed in the upcoming release of LiteSpeed.

Here is a temporary solution, verified by LiteSpeed support:

  1. Edit the file /plugins/litespeed-cache/litespeed-cache.php, around line 138. Locate:
  2. Create a PHP file in your root WordPress directory (where wp-config.php is located) and name it esi_nonce_purge.php. Insert the following code into the file:
  3. Set up a system cron job to run every 1 or 5 minutes:

This process checks the validity of the nonce and purges the ESI tag for wp_rest if invalid, allowing it to generate a new nonce. Note that this solution only applies if you are using LiteSpeed Enterprise (not LiteSpeed Open Source, which does not support ESI).

Content Awareness Isn’t Working

The content awareness feature works by obtaining the ID of the post on which the user is located and retrieving the content of that page. Therefore, if the content from your post 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.

To check content visibility, you can enable the developer tools in the AI Engine settings. In the new 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. In this case, 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.

Chatbots Not Working On Live Website

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.

Not Working
Working