HelicalInsight API Metadata Save Failure and Cache Disable Issue

#1

Hello, how can I completely disable the cache?

I modified cache.xml, refreshed the cache settings, and restarted the service, but Helical still reports cache-related errors.

I want to disable the cache because I keep getting errors when saving the metadata of an API data source. My original API data source was able to create and save metadata successfully. However, after I modified queryParams, I created a new data source and tried to save it, but it failed with an EfwServiceException.

Even if I change queryParams back to the original settings, the same error still occurs. I also cleared the cache, but the error remains.

how can I completely disable the cache
#2

Hi Ruose,

Thank you for your question.
Based on your description, it appears that you have already followed the correct steps to disable caching by:

  • Setting <enableCache>false</enableCache> in cache.xml
  • Refreshing the cache settings

Make sure you restart the helical insight service/docker to make sure this settings gets applied. If these steps have been completed, then the cache should already be disabled.

However, from the behavior you have described, this does not appear to be a cache-related issue. Disabling the cache is therefore unlikely to resolve the metadata save failure.

Since you are using an API data source (HTTP Driver), we have observed that if the metadata or configuration of an existing HTTP connection becomes inconsistent (for example, after modifying queryParams), it may continue to exhibit this behavior even if the parameters are reverted to their original values.

Our recommendations are:

  1. Clear your browser cache.

  2. Clear the Helical Insight application cache from the admin page.

    a. Log in to the application with administrator privileges and navigate to the Home page.
    b. Locate the Cached Reports and Cached Data sources cards, which display the number of items currently in cache.
    c. Click the three dots (details) to open the selective management menu.
    d. Choose to selectively delete specific reports, refresh their status, or delete all resources at once.

  3. Create a new HTTP/API connection from scratch instead of reusing the existing one.

  4. Generate the metadata again using the new connection.

As a best practice, if an existing API connection is working correctly, we recommend not modifying that connection directly. Instead, keep the existing connection unchanged and create a new connection when you want to experiment with changes such as adding or modifying queryParams, headers, authentication, or other connection properties. This helps avoid impacting a working configuration and makes troubleshooting much easier.

Could you also share the following information?

  • Which Helical Insight version are you using? You can see that from the home page when you login as admin/hiadmin
  • What is the exact error message you receive while saving the metadata?
  • Please share the relevant application logs (or the complete stack trace) corresponding to the error.

This information will help us identify the root cause more accurately and determine whether the issue is related to a known behavior in an older version or something specific to your configuration.

We look forward to your response.

Thank you