icy-market-92637
11/29/2025, 2:16 PMnarrow-planet-91101
11/29/2025, 5:48 AMnice-lion-7108
11/28/2025, 6:43 PMgentle-policeman-89141
11/28/2025, 2:02 PMbetter-optician-3834
11/28/2025, 12:05 PMearly-dusk-81683
11/28/2025, 6:43 AMbetter-optician-3834
11/28/2025, 6:10 AMwonderful-monitor-65437
11/27/2025, 8:45 PMfuture-quill-28503
11/27/2025, 8:17 PMbrash-journalist-69902
11/27/2025, 5:58 PMaloof-napkin-97210
11/27/2025, 3:43 PMwonderful-monitor-65437
11/27/2025, 2:45 PMbig-wire-17689
11/27/2025, 2:06 PMflaky-ability-56989
11/27/2025, 10:47 AMstrong-grass-42185
11/27/2025, 9:46 AMbreezy-belgium-57865
11/27/2025, 9:24 AMbrash-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 PM