brash-journalist-69902
11/26/2025, 8:17 PMbland-solstice-21747
11/26/2025, 5:35 PMcold-pilot-71791
11/26/2025, 3:37 PMloud-pharmacist-30125
11/26/2025, 2:51 PMbig-wire-17689
11/26/2025, 1:44 PMaloof-napkin-97210
11/26/2025, 1:27 PMflaky-ability-56989
11/26/2025, 1:19 PMloud-pharmacist-30125
11/26/2025, 8:04 AMloud-crowd-60573
11/25/2025, 4:01 PMaloof-napkin-97210
11/25/2025, 3:55 PMworkflow.client_data.
2. Ticket Data Aggregation: Concatenating all data (profile, problem, AI blockage reason) into final variables for the ticket: workflow.ticket_title_final, workflow.ticket_description_final, etc. The conversation ID is stored in workflow.botpress_conversation_id using robust fallback logic to ensure a valid ID (e.g., convo-8) is available.
3. Transfer: The flow transitions to a node containing the Start HITL card, which targets the internal Botpress Human Handoff Dashboard (no external ticketing system is used).
### 🚨 The Problem
When the Start HITL card is executed:
1. The user sees the successful escalation message, confirming the card starts execution.
2. Immediately after the message, the flow crashes and the user receives the generic error: "Sorry, an error occurred. Please try again later."
3. Crucially: No ticket is created in the Botpress Human Handoff Dashboard.
### Request for Assistance
Since all required variables are correctly transmitted, the failure must be occurring in the internal Botpress logic when it attempts to create the ticket resource for its own dashboard.
Has anyone encountered this specific failure when using the internal Botpress Human Handoff Dashboard? Are there any known issues regarding the format of the User ID (UUID) or the required permissions that might cause the internal ticket creation API call to fail silently?magnificent-london-18710
11/25/2025, 3:03 AMprehistoric-airline-35248
11/24/2025, 7:10 PMicy-market-92637
11/24/2025, 5:51 PMbillowy-morning-42410
11/24/2025, 2:17 PMenough-dog-47566
11/24/2025, 11:54 AMfuture-father-35487
11/24/2025, 12:12 AMflaky-iron-27969
11/23/2025, 11:38 PMconsole.log(event.payload)
const userResponse = event.payload.value
const selectedTitle = event.payload.text
// Log the payload values for debugging
console.log(‘🔍 Payload value:’, userResponse)
console.log(‘🔍 Payload text:’, selectedTitle)
// Save in workflow.RightType
workflow.RightType = userResponse
console.log(‘✅ Interactive response captured:’, userResponse)
console.log(‘📝 Selected title:’, selectedTitle)
console.log(‘💾 Response saved in workflow.TipoDeDerecho:’, workflow.TipoDeDerecho)
and this is the botpress bot log
[whatsapp] WhatsApp handler failed with status 500: Error while handling request:
more details in the doc
I have another bot that this doesn't seem to affect, and it's exactly the same code for handle. but older whatsapp version
https://cdn.discordapp.com/attachments/1442298176236421202/1442298176420839464/message.txt?ex=6924ec59&is=69239ad9&hm=f839dbd4ed7434baad19a0f365e30b56f54a0e169e19590e8394ec6fb3ae772d&powerful-summer-70024
11/23/2025, 5:29 PMeager-kite-3176
11/23/2025, 7:15 AMbig-wire-17689
11/22/2025, 5:27 AMimportant-spring-86151
11/21/2025, 7:11 PMloud-crowd-60573
11/21/2025, 4:00 PMloud-crowd-60573
11/21/2025, 4:00 PMloud-crowd-60573
11/21/2025, 3:26 PMbrief-ambulance-57007
11/21/2025, 1:42 PMaloof-napkin-97210
11/21/2025, 9:39 AMHITL_Direct_Workflow.
### 🎯 Objective:
Trigger HITL_Direct_Workflow via a Global Trigger based on a simple incoming message text ('hitl').
### ❌ Issue Encountered:
The trigger is created, but when typing 'hitl' in the chat, the workflow does not activate (the conversation stays in the Main Flow or terminates).
### 🛠️ Solutions Attempted:
1. Trigger Used: Custom Trigger (advanced) (I chose this because Intent Triggered is disabled, as shown in the attached image, and I want to avoid using Webhook Event if possible).
2. Configuration:
* Event Type: bp/webchat/message/incoming (Listening to incoming messages).
* Condition/Filter Expression: {{ event.payload.text == 'hitl' }}
* Target Node: Points directly to the Entry node of my HITL_Direct_Workflow.
3. Validation: The HITL_Direct_Workflow is currently grayed out (inactive) because it is not called by the Main Flow, confirming it relies entirely on the Global Trigger for activation.
### ❓ My Question to the Experts:
Is there a specific restriction preventing a Custom Trigger (advanced) from listening globally to bp/webchat/message/incoming when its target workflow is inactive/secondary?
Should I use a different event type or wrap the condition differently?
Any guidance on how to force the activation of an isolated workflow via a simple keyword filter would be greatly appreciated!
Thank you!chilly-apartment-48668
11/20/2025, 4:11 PMcareful-manchester-82797
11/20/2025, 4:03 PMmodern-gigabyte-76994
11/20/2025, 1:16 PMhallowed-branch-68168
11/20/2025, 10:20 AM