Khoros Global Support Home Start a conversation Sign in
Start a conversation
  1. Khoros Aurora
  2. Troubleshooting
  3. Known Issues

Custom Components Continuously Reloading when SDK Plugin Preview Is Enabled

Overview

When the SDK key is enabled, you may observe that several custom pages begin to reload continuously. In the browser console you’ll likely see that the “Out of the Box” components are being loaded repeatedly. Disabling the SDK key causes the pages to load normally.

Symptoms include:

  • Custom pages keep refreshing / reloading without user action.

  • Console logs show repeated loading or initialization of OOTB (out‑of‑the‑box) components.

  • Disabling the SDK key stops the reload loop.

  • The issue is present in versions prior to 25.9.


Fixed in Version: 25.9

Resolution Steps

  1. Verify Your Current Version:
    • Check if you are running version a version before 25.9 where this defect was present.
    • You can do this by navigating to the below URL (just replace [your-community-domain])
      https://[your-community-domain]/t5/s/status/version 
  2. Upgrade Your Instance:
  3. Post-Upgrade Steps:
    • Clear your application and browser caches completely.
    • Log out of your instance and log back in.
  4. Verify Resolution:
    • Test the affected pages to confirm they load without reloading issues.
    • Confirm that the SDK key can be enabled without triggering reloads.

Summary

If your custom pages reload continuously when the SDK key is enabled, the cause is a known defect in versions prior to 25.9. To resolve: check your current version, upgrade to 25.9 or later, clear caches, re‑login, and then test. After applying the fix the reload loop should stop.

FAQ

Q1: What happens if I cannot upgrade immediately?
A1: If you cannot upgrade, a temporary workaround is to disable the SDK key, which stops the reload loop. However this may limit functionality tied to the SDK key until you upgrade.

Q2: Will clearing only the browser cache be sufficient?
A2: It’s recommended to clear both application-level caches (if applicable) and browser caches, as stale assets or scripts may persist otherwise.

Q3: After upgrade, pages still reload — what should I check?
A3:

  • Ensure you correctly logged out and back in (session context refreshed).

  • Verify that the version displayed via /t5/s/status/version is truly 25.9 or greater.

  • Ensure no custom scripts or extensions conflict with the SDK key behaviour (especially if page reload logic was customised).

Choose files or drag and drop files
ai_initiated
atlas_studio
kb_automation
Was this article helpful?
Yes
No

  1. Ciprian Nastase

  2. Posted
  3. Updated

Comments