
Announcements
Following up on our previous communication, I have connected again with the product team regarding the ongoing issue. They have provided an additional suggestion that may help.
If the current workaround hasn’t resolved the issue, you can try using a lower value such as:
?page-intelligence.cloneDatasetPayloadSize=18000000
This should be tested during quieter times on the environment (reduced load, minimal background activity), although please note that this is not a guaranteed solution.
The good news is that the product team is actively working on a permanent fix and has confirmed that they are targeting a rollout by end of July. They will continue to keep us informed on progress, and I will share any updates with you as soon as I receive them.
As there are currently no further actions pending from the support side, and we now have a tentative ETA from the product team, I wanted to kindly check if we can proceed with temporarily closing this case for now. Please rest assured, should the issue persist, or new developments arise, we can always reopen the case and continue the investigation.