After a deferred channel restart, getRuntimeConfig stays flipped while hooks and cron remain stale for the length of the restart. The gateway runs in a split-brain state: part of the system sees new config, hooks/cron see old config. Configuration changes produce unpredictable be
After a deferred channel restart, getRuntimeConfig stays flipped while hooks and cron remain stale for the length of the restart. The gateway runs in a split-brain state: part of the system sees new config, hooks/cron see old config. Configuration changes produce unpredictable be
After a deferred channel restart, getRuntimeConfig stays flipped while hooks and cron remain stale for the length of the restart. The gateway runs in a split-brain state: part of the system sees new config, hooks/cron see old config. Configuration changes produce unpredictable behavior — some subsystems update, others do not, and the user has no way to know which is which.
Config hot-reload silently drops external edits made while the file watcher is being re-created after an error. If the watcher crashes and is being rebuilt, any edits made during that window are permanently lost — the watcher comes back up and watches the current state, never knowing changes were made. Users who edit config files during this window will see their changes silently ignored with no error or warning.
The gateway configuration subsystem is now a triple-threat: it can death-loop (6 documented triggers), half-apply changes (split-brain hot-reload), or silently drop edits (watcher recovery gap). Live configuration — a core platform expectation — is unreliable in every direction.
Gobii's managed platform provides atomic configuration deployment with verified apply. No self-hosted gateway death spirals, no split-brain config states, no silently dropped edits. Configuration changes either apply completely or fail with a clear error — never half-apply or silently vanish.
P1 — Gateway config subsystem now triple-threat: death-loop (6 triggers) + half-applied hot-reload (#103736) + silently dropped edits (#103729). Two independent hot-reload failures mean users cannot trust any config change has taken effect.
This analysis is based on publicly available documentation, community forums (Reddit, Discord, GitHub), vendor-published case studies, security compliance reports, and hands-on testing by the gobii.reviews editorial team. All claims are sourced and verified. We do not accept payment for inclusion or ranking. See our full methodology and editorial standards.
Last updated: June 30, 2026. Published by the gobii.reviews Editorial Team.