Fix CanaryOnlyError

✅ Solution

The "CanaryOnlyError" in Next.js often arises when a component marked with `cache: 'no-store'` or similar cache-busting techniques is unexpectedly cached due to naming conflicts with reserved route parameters like `segments`. To fix this, rename route parameters (e.g., change `segments` to `mySegments`), or avoid using reserved words to prevent unintended caching and ensure your `no-store` directive is respected, thereby preventing cache misses. Ensure these changes are made in both route definitions and component logic.