Hello team,
We are experiencing an issue with the view_count field in the Community table, where the value is unexpectedly changing to 2147483647.
There are no logs or audit records indicating what is updating this field or why the value is being changed. This is causing errors, as the value does not reflect the actual number of views.
One important detail is that the affected records have very low actual view counts (for example, 2 or 10 views), but their view_count values suddenly change to 2147483647.
Since 2147483647 is the maximum value of a signed 32-bit integer, we suspect that something may be incorrectly setting the field to this value rather than it being a normal counter overflow caused by a high number of views.
As a temporary workaround, we executed a Fix Script to restore the correct view_count values for all affected records. However, the issue continues to occur, and additional records are being affected.
This behavior started after the upgrade to the Australia release, and we are trying to determine whether it could be related to a defect or a change in the OOTB Community functionality.
So far, we have not been able to identify the root cause or determine what process is updating this field.
Has anyone experienced a similar issue, or could you provide guidance on what might be causing this behavior, how we can trace these unexpected updates, and what could be done to permanently resolve the issue?
