Segment loading new rows with delay after update to v7.7.0

We recently updated to v7.7 (used to be 7.8 but rollbacked because of this problem, won’t be able to update to v7.9.1 before at least next week), and rollbacked to v6.x because of this issue.

Expected behavior

When adding a new row in DB, it should appear in forest when reloading a segment/view that should display it.

Actual behavior

There’s a delay (multiple 10s of minutes) between the object creation in DB and it appearing in segments and sometimes views. This blocks usage of some smart actions that are enabled for objects of a segment.

Failure Logs

None found.


Please provide any relevant information about your setup.

  • Package Version: 7.7.0
  • Express Version: 4.17.1
  • Sequelize Version: 5.15.1
  • Database Dialect: postgres
  • Database Version: 9.6
  • Project Name: Platform

Hi @cberez,

If I understand well:

  • 7.7 version shows a “delay issue”, as a cache invalidation delay mechanism.
  • You are in 6.x now to avoid the “delay issue” encountered in 7.7
  • You will jump to 7.9.1 next week

Forest does not have any caching mechanism for your data. As the database return differents records, Forest displays different records.

Was the delay seen in 7.7 only?
Do you have any replica or follower mechanism on the database? Is Forest plugged on the same unique database address as your database client tool?


Hello @Sliman_Medini

Only noticed the delay issue in 7.7 yes, all is well in 6.x. Issue happens on all environments where 7.7 is deployed, including local in dockerized DB.

We don’t have any replica or follower mechanism on the database, Forest is plugged on the same unique DB address as the DB client tool (using the exact same connection string) and all went well in the previous versions.

I’m trying to update to 7.9 today, I’ll report here if the issue is still here.

1 Like

Hello @cberez

Thank you for the heads-up. I’m looking forward to hearing more from you.


Hi @Sliman_Medini @morganperre,

Tried locally and can’t reproduce with 7.7
Updated to 7.9.1 and it looks OK for now, can’t reproduce either, we deployed it to all our envs after validation checks

I guess we can close this :slight_smile: