Hi,
We've recently enabled proactive caching refreshing every 10 minutes and have seen data in locked versions changing after Full Admin Optimization runs. Given how the data reverts back to a prior submitted number, I suspect having proactive caching occur while the Full Admin Optimization runs may be the culprit.
here's an example to depict what is happening.
original revenue is $10M.
user submits new revenue amount of $11M.
version is locked.
data in locked version is copied into a new open version.
full optimization runs at night and take 60 mins. all the while, proactive caching runs every 10 mins.
user reports the revenue in the previously locked version is $10M and the new version shows $11M.
We've never experienced this prior to enabling proactive caching which leads me to believe the 2 processes running concurrently may be the source of the problem.
Is proactive caching supposed to be disabled while Full Admin Optimization process is running?
Thanks,
Fo