A background repolling issue that persisted after customer frontend navigation has been fixed as of the 2026-07-21 platform release (CB-1191). The platform no longer performs unnecessary background data requests after you move between pages.
✨ What's New
Previously, background repolling processes continued running even after navigating away from the originating page in the platform. This caused unnecessary network activity and could result in degraded performance — such as slower page loads or data appearing to refresh unexpectedly — while you were using a completely different section of the platform. The fix, shipped as part of the Core / Churn Buster release on 2026-07-21, ensures that background repolling stops as expected the moment you navigate to a new section of the platform.
🛠️ How to Use It
No action is required on your end. This fix has been applied automatically to the platform. Simply continue navigating the platform as normal — background processes will now correctly stop when you move between pages.
📋 What to Expect
Background repolling will no longer persist after navigating away from a page. There are no changes to the visible interface or your existing workflows. If you previously noticed slower performance or unexpected activity while switching between platform sections, this fix addresses that root cause.
🔍 Troubleshooting Related Issues
If you believe you are still experiencing unexpected background activity or performance issues related to page navigation after 2026-07-21, here are steps to help identify and report the problem:
- Note the specific page or section where you observed the issue (e.g., which part of the platform you navigated away from and which page you navigated to).
- Record the exact behavior you noticed — for example, slower performance, unexpected network activity, or data appearing to refresh after navigation.
- Note the timestamp when the issue occurred so our team can cross-reference platform logs against the CB-1191 deployment.
- Check if the behavior is reproducible — navigate away from the same page again and observe whether the issue repeats.
Having this information ready — particularly the affected page, a description of the behavior, and the timestamp — will allow our team to investigate quickly if escalation is needed.
If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.