There's an issue with cache invalidation. Current logic invalidates the cache based on the block height and the number of executions in the database. If a number of executions is lower in the database than in the cached emulator block height then it obviously needs to be reset. The problem is that there's an edge case where other executions are done after reset so the height matches.
There's an issue with cache invalidation. Current logic invalidates the cache based on the block height and the number of executions in the database. If a number of executions is lower in the database than in the cached emulator block height then it obviously needs to be reset. The problem is that there's an edge case where other executions are done after reset so the height matches.