mirror of
https://github.com/langbot-app/LangBot.git
synced 2026-10-23 08:55:44 +08:00
Boot continues for minutes after the first directory snapshot is committed: platform ports reconnect, knowledge bases and pipelines reload, and a cold shared Runtime restore may still be running. The refresh loop only started at the end of that stage, so any boot slower than the projection staleness window failed closed while restoring knowledge bases, and Core then exited during startup - every retry hit the same window. Start the single refresh task as soon as the first snapshot is committed and keep the later start as a guarded fallback so the loop is never created twice. Observed on the production Cloud instance: a boot that took ~120s to reach knowledge base restore raised 'Cloud directory projection is stale' and the process exited, while the same image had booted earlier with a faster start. Co-authored-by: multica-agent <[email protected]>