Hi again,
just wanted to follow up here - not sure if it’s 100% related, but there has been an issue identified with Insights in 7.7.0 with users not having named timezones in the MySQL DB; 7.7.1 has that fixed, so maybe this also applied to this problem.
Since we already did the perceived fix to this issue in your other topic, I’m inclined to close this one here, but, just to verify that, can you please try to re-enable the Insights feature and see if this problem still persists?