Since Sept 2 we can't publish our production bot. Studio shows: Failed to publish bot: quota exceeded Workspace is on the community plan. bot_count is 2/1 and workspace_member_count is 2/1. What we see via the API: publishing DOES write a new deployments/*.json artifact every time, with the correct content (8 written today). But the bot's deployedAt is frozen at 2026-09-02 12:39:41 UTC and never advances, and the runtime keeps serving the definition from that date — confirmed by reading the exact context sent to the model in improvements/iterations/. The odd part: we published successfully many times with these exact same quota values (2 bots, limit 1) right up to Sept 2 at 12:39 UTC. Nothing changed on our side — no new bot, no new member. It just stopped working. That looks more like an enforcement change or a bug than a limit we just hit. Questions: (1) Which quota actually blocks the publish — bot_count or workspace_member_count? (2) Did enforcement of this change around Sept 2? (3) Any chance of a temporary grace period? We have a public open-day event on Sept 18 and the fixes are already written and waiting. (4) Is there a supported way to deactivate or archive a second bot without deleting it? updateBot exposes a

blocked

boolean but it is undocumented — would that free bot_count, and is it reversible? (5) Can a bot be moved to another workspace? Happy to share workspace and bot IDs privately. Thanks!

The bot quota appears to be the blocker here, not the workspace-member quota. Botpress treats Bot Count and Collaborators as separate limits, and the current PAYG/Community allowance is 1 bot. The fact that deployments are still being written while "deployedAt" remains frozen strongly suggests the publish/enforcement path needs investigation. I can help trace the quota check, deployment artifacts, and bot state to determine whether this is a quota enforcement change or a Botpress-side issue, and identify the safest way to free/move the bot without losing it. @better-nest-13340