Yet another node offline after update thread

yeah, thank you for the follow up. These problems with time hazard (which is the thing, I believe) can be triggered by very unrelated parameters and looks like I have a “correct environment” for the problem now :slight_smile:

I have opened the issue on GitHub, hopefully under the correct project.