fix(plugins): Talk and plugin-loading requests fail on PostgreSQL Gateways (#201976) Settled plugin migration readiness was cached only under the deferred migration receipt. Since that receipt became a peek, it stays absent until a migration write publishes one, so the worker's startup read was never reused and every synchronous plugin load reread the ledger on the Gateway thread. PostgreSQL refuses that read, which left Talk "warming" and failed other plugin-loading requests with "must run in a worker". Key unpublished readiness by the current state read admission instead. Migration writes still publish a new receipt, and closing or replacing the database retires the admission. Closes #201969 Co-authored-by: VACInc <3279061+VACInc@users.noreply.github.com>
Current
·
C2
·2026-11
fix(plugins): Talk and plugin-loading requests fail on PostgreSQL Gat…
Find Your Interest
- fix: let PostgreSQL Gateways start with plugin-backed secrets (#201063)
- “We’re making real incremental progress. We continue …
- fix: saving an agent no longer looks failed while a plugin reload is …
- fix: install official plugins from the chat card without leaving the …
- fix(voice): Discord controls and phone consults fail with PostgreSQL …
- fix(update): supervised PostgreSQL updates ignore server recovery cap…
- fix: let automatic updates finish plugin updates that an earlier upda…
- fix(agents): node tools with an unverified plugin owner can pass plug…
- fix(ui): hide plugin toolbar actions in the resting phone composer (#…
- fix: keep plugin details responsive while inventory loads (#201792)
Current
·
C2
·2026-11






