BLISS tree structure is not always maintained in Redis
We noticed Flint can get stuck at start up. That's the same for the F5 data display.
It sounds like the tree created by BLISS in Redis can be removed partially. So nodes could remain without parent or expected children.
- This create issue on Lima Redis data node
- Which looks to be iterated at initialization of the Redis client (for example Flint)
- And break to the new-scans listener
Occurred on ID10, ID11, ID15, ID19