https://discord.gg/botpress logo
Bot works in emulator but freezes in web chat – me...
# 🤝help
a
Hi, I’m having an issue with my bot. The bot works correctly in the Botpress emulator, but when I test it in the Web Chat, it freezes after clicking an option. The user message shows as “Delivered” but the bot does not continue. In the Events inspector, I see multiple
message_created
events failing with error 502: [Internal] Request failed with status code 502. This happens consistently in web chat but not in the emulator. What I already tried: - Republishing the bot - Checking AI Transitions - Verifying variables and flows - Confirming the bot is active Could this be an internal Botpress issue or a web chat runtime problem? Thanks in advance.
Hi! Just following up on this issue. It’s still happening in Webchat (502 message_created), while Emulator works fine. Happy to provide more details or screenshots if needed. Thanks!
l
Can you drop your workspace ID?
a
Here is my workspace ID: bbe41de2-64de-4b89-b138-ddf24d9f3316
webchat working fine for me
please try clearing cache + session data!
a
Thanks for checking. To clarify: the initial menu renders correctly in Webchat (same as in Emulator). The issue happens AFTER clicking any option. Steps to reproduce: 1. Open the published Webchat 2. Wait for the welcome message 3. Click any button (e.g. “Elegir un curso” or “Bot para mi negocio”) 4. The user message shows as “Delivered” but the conversation does not advance Important: - This happens ONLY in Webchat, not in Emulator - I already tested disabling the AI Transition in the target block - The issue persists even with AI Transition disabled - The button is correctly connected to the next block This suggests the issue occurs after button interaction, not during initial render. Happy to provide a screen recording if needed.
Hi, just checking in again. This issue is blocking my production bot. The flow works in Emulator but freezes in Webchat after clicking any button. Is this a known Webchat issue, or should I open a GitHub issue instead? Thanks.
l
Will do more testing soon and get back!
hey @ambitious-policeman-67184
are you using a new workspace?
bbe41de2-64de-4b89-b138-ddf24d9f3316 is no longer working for me
2 Views