Hi all – hoping someone here has run into this before because I’ve spent most of the evening chasing it. Context: I have a Botpress bot that has been running for a long time using the Slack integration v0.4.3. Yesterday the Slack integration was deprecated/broken by an update, so I upgraded the bot to Slack integration v4.0.1. After the upgrade we rebuilt the Slack auth and scopes and successfully reinstalled the Slack app using the new OAuth flow. Current state: • Slack events are received correctly • Botpress processes the workflow correctly • Botpress generates the outgoing text reply correctly • Slack user profile lookup works • Botpress can mark messages as seen However the actual outbound message creation fails every time. Typical log sequence: Sending Message. Type: text. Text: SUCCESS: State Reset Then immediately: Error creating message An unexpected error occurred in the integration code: 400 type: Runtime Important detail: I reproduced this with a completely blank new bot using the same Slack app. That bot simply: receives a Slack DM sends a plain text reply Even that fails with the same Error creating message runtime error. So it doesn’t appear to be related to my original workflow. Other observations: • Slack event subscriptions work • Slack webhook verification works • Slack profile fetch works • The integration successfully registers and exchanges the refresh token • Only the final chat message send fails Example payload that fails: {"type":"text","text":"Hello! How can I help you today?"} Has anyone seen the Slack integration receive messages but fail to send replies like this after upgrading to v4.x? Or is there something subtle about the new Slack auth/token rotation that could cause this? Any pointers appreciated – I’m currently stuck with a bot that can receive Slack messages but cannot reply. Thanks!

Will take a look! It was a bug with the integration!

Thanks @loud-crowd-60573 , I'll have a look after my dinner!