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 does not reply to the user’s first new question after the ticket is closed. In the attached example, the user selected “Positive” and then asked, “I would like to know what programmes do you offer?”, but the bot remained idle. the bot will only reply after the user send a second msg https://cdn.discordapp.com/attachments/1546463462153265153/1546463462400598057/image.png?ex=6a9fdfd5&is=6a9e8e55&hm=20cf13e53cf3cb841c9b44ad08a30362965cf36ef9cb0ff8ced9f55b6c648237&

I'm seeing the Agent Assigned Timeout setting on the hitl plugin (v2.0.2) not fire as expected. Setup: Plugin: hitl v2.0.2, installed alongside desk-hitl for Botpress Desk escalation Config: Agent Assigned Timeout = 150 seconds, Agent Assigned Timeout Message set to custom text, Continue Flow on Session End? = ON, Use Human Agent Info = ON Steps to reproduce: - Trigger escalation via the Escalate To Desk tool from an AutonomousNode (user asks for a human) - Bot confirms transfer, ticket is created in Desk - Do not assign/reply to the ticket in Desk - Wait past the configured timeout (tested at 150s+, waited up to ~200s) **Expected: **The Agent Assigned Timeout Message should be delivered to the user automatically once the timeout elapses, and control should return to the bot flow (per Continue Flow on Session End). Actual: No message is ever delivered, whether waiting passively with the webchat tab open, or sending a follow-up message from the user after the timeout window has passed. Already ruled out: - Confirmed the config is saved correctly (checked via Integration Hub → Installed Integrations → hitl → Configuration) - Tested with the bot's "Always Alive" setting both disabled and enabled.. same result in both cases, so it's not a cold-start/sleep issue - Confirmed escalation itself works correctly (ticket created, transfer message delivered, Desk integration functioning) Bot ID: 99d5f775-83b6-40f1-8774-10eb33062a25 Please help! https://cdn.discordapp.com/attachments/1546420854982840410/1546421182180368394/image.png?ex=6a9fb874&is=6a9e66f4&hm=eb93abd3fa95903b2f40c87b1b0d929def27a3a45cbf08807a19eaaac5711d5a&

I tried to log in today to check conversations on my running bots and wasnt able to acces my old workspaces . a legend : Not available on Viber - requieres the latest pricing is blocking me I was working on my bots yetserday late night and suddenly today , I am locked out from all workspaces and running bots and i need toc heck several things urgently . Please advise ASAP https://cdn.discordapp.com/attachments/1544728929594507334/1544728930152484924/image.png?ex=6a99906c&is=6a983eec&hm=50de566767b244e5ddb2b0d37437db02c9e99aeba39ff2f341a348ad8f1a927f&

I need a strict time-based WhatsApp workflow using the Asia/Dubai timezone. The AI must reply only from 11:00 PM to 10:00 AM. From 10:00 AM to 11:00 PM, it must send no automated replies so our human team can respond. Instructions and escalation rules did not enforce this schedule. How can I configure this automatically in Botpress Vibe?

Hi, I'm trying to connect Botpress Desk to our existing WhatsApp number (already connected to Botpress Studio via the Cloud API), but I'm running into an issue. Setup: - We have a 'New Agent' bot in Studio, with the WhatsApp integration (number +90 543 629 42 63) connected via OAuth and working fine. - When we use the 'Escalate To Desk' card, we get an error. The full error text from Studio's Issues panel is: "This bot is not connected to Botpress Desk. Enable it on the Deflecting Bots page in Botpress Desk, then republish." - In Botpress Desk (desk.botpress.cloud), we tried connecting via Settings > Channels > WhatsApp > Connect. - In Meta's embedded signup pop-up, we tried "Connect with your existing WhatsApp Business app" and entered +90 543 629 42 63, but got "Number not found - not associated with a WhatsApp Business app" (the number isn't on the consumer app, it's already registered via the Cloud API). - "Start with a WhatsApp API account" only offers two options: the same "existing app" flow (same error) or "add a new number" (haven't used this, don't want to risk our real number). We repeated both attempts, same result each time. - Our business verification (SonarHouse) was completed on August 29, 2026. We waited a couple of days in case Advanced Access hadn't propagated yet, tried again — same result. - In one earlier attempt, the number that ended up connected to Desk by mistake was +1 555-399-6811 — looks like a Meta test number, not our real one. - Checked Meta Business Manager: the "Botpress" partner (Code: 416465769304058) already has "Full access" to our WABA (SonarHouse Electronic Music School, code: 158252431546592), so permissions don't seem to be the issue. Question: How can we connect an existing WhatsApp number — already linked to Studio via the Cloud API — to Botpress Desk, without risking our real number? Is there an alternative, like manually entering a WABA ID / access token?

How do you handle muting the bot during a human handoff? The issue is that after the bot flow ends and an agent takes over, any new message from the user triggers the bot to restart its flow from the beginning, disrupting the live chat.

Hola, tengo dos canales de mensajería configurados en mi agente "Luxuren" (Viber) que no funcionan: 1. Twilio: conectado correctamente (Account SID/Token guardados, "Connected"), webhook configurada en ambos lados. Al escribir por WhatsApp Sandbox, Botpress recibe el mensaje y lo procesa (aparece en Conversations), pero nunca llega la respuesta. En el Debugger de Twilio aparece el error 12300 - Invalid Content-Type: la respuesta de la webhook de Botpress (https://webhook.botpress.cloud/...) viene como application/json, y Twilio la rechaza porque espera TwiML. 2. WhatsApp (Meta, vía OAuth embedded signup con coexistencia activada): la conexión muestra "Connected" en Channels, y los mensajes SÍ llegan a mi WhatsApp Business App (coexistencia funcionando), pero NO aparecen en absoluto en "Conversations" del agente — parece que el webhook de Meta a Botpress no está entregando el mensaje. ¿Podéis revisar ambas integraciones?

Hey everyone I made some CSS changes a few weeks back. Last week, I wanted to make more, but kept running into an issue. I'd add custom css in Appearance, and click Publish Changes. Everything seemed fine until I'd reload, and all of those changes were gone. After a number of hours poking around, somehow those CSS changes stuck, but the current published styles are incorrect. Like, very incorrect (the text and speech bubbles are the same color, which means its unusable) I've been trying to update changes again, but running into the same issue, where changes are wiped out when I reload after pressing "Publish Changes". Attached is a video showing the issue. Any feedback is appreciated! https://cdn.discordapp.com/attachments/1542158535373234246/1542158536245780510/botpress_css_issue.mp4?ex=6a90368e&is=6a8ee50e&hm=baa8cb8ac9253b10a4b10480550f3d0ebcac7fde62928d423b8d946ed91bb0d0& https://cdn.discordapp.com/attachments/1542158535373234246/1542158536992096362/Screenshot_2026-08-26_at_9.01.15_AM.png?ex=6a90368f&is=6a8ee50f&hm=3370de186aebf48fb4153f26b92b28bd1b88af69421a563bc1e9d05fe58186b1&

Hey everyone! New here .. I'm building a knowledge-based chatbot SaaS (FastAPI backend, Groq for inference) and looking into multi-tenant architecture patterns. Was checking out Botpress as a reference for how you all handle KB integration + tenant isolation. Is this an okay place to ask a few architecture questions, or is there a better channel for that?

I'm currently using the Free plan. I saw this warning: "You've used 95% of your AI spend. Upgrade to avoid hitting your limit." My Conversations count is still below the 100-conversation limit, but my AI spend is already close to $10. I asked the Botpress AI support bot about this, and it said that I don't need to worry about the AI spend limit as long as I stay within the 100 Conversations limit. However, my Workspace is showing a red warning about the AI spend, so I'm not sure which limit actually matters. Does anyone know if the Free plan can still be used after the AI spend goes over the limit, as long as the Conversations count is still below 100? Thank you for your help. https://cdn.discordapp.com/attachments/1541646400817991760/1541646401077772399/20260825.jpg?ex=6a8e5998&is=6a8d0818&hm=dff474bdc230f61e2a0facd96e445b479da663e1101c8c0a16a8380aaebde365&

Resumen: El botón "Publish" se queda cargando indefinidamente y termina en "Publish failed", sin más detalle en pantalla. Bot ID: 5acc2946-64ca-4f44-9625-cf6b2676db8c Pasos ya probados (sin éxito): Hard refresh (Ctrl+Shift+R) Ventana de incógnito nueva Eliminar la herramienta "Search Knowledge" del nodo Autonomous (no había ninguna Knowledge Base creada) Errores relevantes en la consola (se repiten igual en ambos intentos): index-BLF9O2gn.js:143 Missing environment variable: (el nombre de la variable no se muestra, el mensaje llega cortado) api.botpress.cloud/v1/chat/states/bot/5acc2946-64ca-4f44-9625-cf6b2676db8c/recurringSyncs → 400 api.botpress.cloud/v1/chat/states/bot/5acc2946-64ca-4f44-9625-cf6b2676db8c/dsData → 400 (se repite varias veces) api.botpress.cloud/v1/chat/events → 400 /api/5acc2946-64ca-4f44-9625-cf6b2676db8c/publish?quick=false → 400 (el propio endpoint de publicar) App-DqUYZaCe.js:7651 AxiosError$1 Nota: El resto de errores en consola (ERR_BLOCKED_BY_CLIENT en Segment, Mixpanel, Sprig) parecen ser solo telemetría bloqueada, no relacionados con el fallo de publicación. Pregunta: ¿Qué variable de entorno falta exactamente, y a qué está asociado el 400 en /publish? El bot usa el template recomendado (Autonomous Node) sin modificaciones estructurales más allá de quitar la herramienta de Knowledge Base.

Hi! My Botpress agent works in the Emulator, and the Telegram integration is connected and enabled.

Autonomous Node with Vision Agent. VisionAgent hook runs (see log — "Extracting content from images") but {{turn.Visionagent.content}} comes back empty, so the node never sees the extracted text. I have "Extract from Incoming Images" on and the Extract Content from Image card added. Could a before_incoming_message hook (I have desk-hitl and an inject_learn hook running) be clearing the turn state before the node reads it? How do I capture the vision output reliably? https://cdn.discordapp.com/attachments/1540211197587099758/1540211198027374623/image.png?ex=6a8920f5&is=6a87cf75&hm=c9c8538e28510858a191556f5b2169dd882aa06df603df40ae63b550b1cff53e&

Publishing ends with "Your bot is live!" and “Last Deployed” remains at 16 days ago. The Studio Emulator runs the latest version, but the production Webchat still uses the previous one. An AxiosError is recorded during each attempt. Report id: report_01M0FYPQKQG46265GKZ8JZH09Z

I followed the official WhatsApp integration procedure documented here using "Authorize WhatsApp". During this process, Meta permanently restricted the newly created business because it detected prohibited automation. Before I attempt Manual Configuration using my own Meta Developer App, I need to know the recommended procedure in this situation. I don't want to create another Business Portfolio or WABA if Meta could consider that circumvention of the previous restriction. Can you confirm whether this is a known issue with the WhatsApp OAuth onboarding process and what procedure Botpress recommends after a Meta Business Portfolio has been permanently restricted during onboarding?

I am looking for the devs for the collaboration. now, I am building the project. by the way, I have faced big problems So I want to find the friends can support me

Problem: The agent is showing “Unpublished changes”, but the “Publish changes” button/option is not visible anywhere — including the Overview page, Get ready to go live checklist, top-right section, or the All agents (3-dots) menu. Expected: The “Publish changes” button/option should be available so the changes can be published and reflected in the live webchat. Steps already tried: Hard refresh (Ctrl + Shift + R) Zoomed out to 80–90% Maximized the browser window Tried Incognito mode Disabled extensions Checked different pages, including Overview, Channels, and All agents Workspace: Piet’s workspace (Community plan) Agent: JP & Tax Associates Agent URL: Please paste the exact URL from the browser address bar here (the agent page URL). Browser/OS: Chrome on Linux Approximate time: Today

Hi, just submitted a bug report (report_01M07RJ0NEN0KTGZ64DQHY40X8) for a custom action whose fetch() calls are failing with "Failed to fetch" on every request, confirmed it's not my code, same failure happens against an unrelated public test endpoint too, and reproduces in the Emulator. Workspace: BENVI Collective, bot: Hage Hall. Would appreciate a hand looking into it when someone's free.

Botpress totally stop working, I cannot ever load the conversation of my workflow that previosly was working.

I'm working as senior AI engineer now. I'm currently looking to expand my business into the United States and Europe, and I'm looking for a reliable native business partner who is interested in building a long-term business together. I'm not simply looking for connections—I'm looking for someone who values trust, transparency, and sustainable growth. Please feel free to contact me a DM anytime. Looking forward to meeting great people!

Hola, tengo un número de WhatsApp Business (+34 872 04 89 99, ID de teléfono: 1223566950836765, WABA: 2480870442386460) que muestra estado "Conectado" en Meta y "OAuth Connection: Connected" en el Integration Hub de Botpress. El bot funciona perfectamente en el Emulator de Botpress (respuestas correctas, flujo completo). Sin embargo, al enviar mensajes reales desde WhatsApp a ese número (probado desde varios teléfonos distintos), no llega ninguna respuesta. En Meta Business Suite, Insights muestra "Mensajes recibidos: 0" para todo el periodo, y en el dashboard de Botpress, el canal WhatsApp aparece como "Never invoked" — es decir, no llega absolutamente nada, ni siquiera un evento entrante. He visto un hilo similar de @Raysha con Messenger (mismo síntoma: OAuth conectado, 0 mensajes). Ahí se sugería revisar si la app de Meta sigue en modo Development, lo que limitaría la interacción a usuarios con rol asignado — ¿esto también aplicaría a integraciones de WhatsApp Cloud API vía OAuth de Botpress, o es un tema exclusivo de Messenger/Facebook? ¿Podríais confirmar si la suscripción de webhook (subscribed_apps) está correctamente activa para este WABA? Llevamos varias horas esperando por si era un problema de propagación tras varios intentos de registro, pero sigue igual. Gracias de antemano.

Hi Botpress Team, We are a Botpress for Good non-profit workspace: Workspace ID: wkspace_01KFJ4NZAB6MHTGV5459F24TJ6 Email: admin@mayasannidhifoundation.online / maayasannidhi@gmail.com Invoice: $27.27 for AI Tokens - 10 days overdue Ticket: #6633 We emailed support but were redirected here as live chat is for Enterprise. We are Maaya Sannidhi Foundation, a small charity. We are requesting a 10-day extension until Aug 24th to clear the invoice. We are also requesting if any additional discount is possible on top of the 25% Botpress for Good discount. Please help us avoid suspension. Thank you so much for supporting non-profits!

Hi! My last question is about Conversation lifecycle / End / timeout. We’re designing a privacy-first lifecycle for our mobile app MindBend, where Botpress Conversations are temporary and eventually physically deleted. I’m trying to understand the exact lifecycle semantics of a Conversation. Our bot has an explicit product End Node that reaches the system Conversation End workflow. A few questions: Once the Conversation End workflow finishes, is that Conversation considered definitively ended? Can a new user message later be sent using the same Conversation ID? If yes, does Botpress effectively resume/reopen the same Conversation, start a new session inside it, or is the intended pattern to create a completely new Conversation? We also use inactivityTimeout: 20 with the system Timeout Workflow. When the Timeout Workflow reaches its End Node, does Botpress also execute the system Conversation End workflow? Is a timeout-ended Conversation lifecycle-equivalent to a Conversation that reached an explicit End Node? Can that same Conversation ID later receive/resume messages? I’m mainly trying to identify what Botpress considers the true terminal state of a Conversation.

After: DELETE /conversations/{id} returns successfully, what should an application treat as authoritative confirmation that the Conversation is permanently deleted? For example, should: GET /conversations/{id} immediately return not found? And should the Conversation immediately disappear from Conversation list/search APIs? Are reads/lists strongly consistent after deletion, or can a recently deleted Conversation remain visible for some period? We want to perform an automated deletion verification rather than assume that a successful DELETE response means all stored Conversation data is already gone.

Related lifecycle question for anyone familiar with the runtime internals. After a Conversation reaches its End Node / Conversation End workflow, is it safe to immediately call: DELETE /conversations/{id} Or can work still be running or queued after the Conversation has logically ended? In particular, could there still be: workflow or Autonomous Node execution Execute Code/actions queued outgoing messages integrations scheduled work custom events hooks/callbacks If I delete the Conversation while any of those are still pending, does deletion cancel them, or could they still execute afterward? And if “Conversation End” does not guarantee that everything is quiescent, is there a supported API/event/state that tells us: “all work associated with this Conversation has finished and it is now safe to physically delete it”? The use case is that Botpress is temporary conversational execution infrastructure for us, rather than long-term transcript storage.

Hi, I’m trying to understand Botpress delivery semantics before automatically deleting Conversations. What guarantees exist for webhook/custom-event delivery? Specifically: Is delivery ordered? Can the same event be delivered more than once? Are deliveries retried after a non-2xx response? Are timeouts retried? Is there a documented maximum retry period / delivery window? Is delivery effectively at-most-once, at-least-once, or something else? Our backend needs to persist the final result of a Conversation before we physically delete the Botpress Conversation, so we need to know when it is safe to regard all required callbacks as delivered. If Botpress exposes a delivery ID / event ID intended for idempotency, I’d also be interested in the recommended pattern.

Hi! We’re implementing a privacy-first deletion lifecycle and I’m trying to understand the exact deletion cascade in Botpress. The documentation says deleting a Conversation immediately deletes its Messages. When calling: DELETE /conversations/{id} does Botpress also permanently delete data associated with that Conversation such as: processed / failed / ignored Events and custom event payloads Conversation variables/state Conversation tags workflow/execution records logs associated with execution analytics records Botpress Tables records that reference the Conversation Or do some of these survive Conversation deletion? Separately, when permanently deleting a Botpress User, what User-scoped data is automatically deleted? For example: User variables / attributes events associated with userId Conversation associations other Botpress-managed User state I’m specifically asking about Botpress-managed persistence rather than data we independently store in our own Tables/backend.

Hi, I've connected my bot using the Zendesk Messaging HITL but had no response from the bot. Steps taken: 1. I use the API Reference from Sunshine Conversations to do a Pass Control request from Zendesk Agent Workspace to the Botpress Integration Switchboard. The request sent a 200 OK response. 2. Then using the Get Conversation request I checked that the Active Switchboard Intregration was updated to the Botpress Integration, which was the case. 3. Then I sent a message through that same conversation but no responde from the bot was received. Extra context: - There is no issue registred in the Botpress Cloud. - The channel which the conversation takes place is a WhatsApp Business account connected to Zendesk. - The Botpress Integrations its succesfully connected to the Zendesk account and has linked the whatsapp channel in which the conversation is taken place. Any ideas of why it's the Botpress bot not responding to the conversation?