polite-egg-96918
10/13/2025, 9:23 PMbrief-sundown-6269
10/13/2025, 6:13 PMorange-dress-24898
10/13/2025, 5:17 PMmammoth-lifeguard-63559
10/13/2025, 11:49 AMminiature-parrot-39655
10/13/2025, 9:41 AMplain-house-72038
10/13/2025, 9:03 AMgentle-policeman-89141
10/13/2025, 7:32 AMnutritious-oil-27998
10/13/2025, 7:29 AMmammoth-lifeguard-63559
10/13/2025, 4:52 AMflaky-iron-27969
10/12/2025, 4:44 AMmammoth-lifeguard-63559
10/11/2025, 10:01 PMdelightful-oil-82370
10/11/2025, 6:49 PMripe-vr-73619
10/11/2025, 1:16 PMquaint-helmet-66870
10/11/2025, 5:57 AMfierce-daybreak-40159
10/11/2025, 12:04 AMminiature-eve-55794
10/10/2025, 6:02 PMwhite-nest-40686
10/10/2025, 3:06 PMconversationId
and userId
to the webhook, but the variables come back empty.
This is the report ID of a test bot: **report_01K2319T24Y7431WZNCR2PGFQE**:
- When the conversation starts, I set a numeric and a string variable.
- I display the variable values in the chat.
- Via Postman I call the botās webhook with two query parameters: conversationId and userId.
- When the workflow is triggered, it reads and then it writes the variables in the chat; but the values are empty string and 0
@loud-crowd-60573 @loud-crowd-60573
https://cdn.discordapp.com/attachments/1426224405343768696/1426224406048276522/image.png?ex=68ea727c&is=68e920fc&hm=1ec93a1381f500240f2b5b8a9388cca71feb3d64132b88ff16d65161e45d6a9a&agreeable-breakfast-45880
10/10/2025, 11:43 AMfast-controller-85245
10/10/2025, 11:29 AMfierce-bear-17255
10/10/2025, 11:26 AMwooden-beard-40210
10/10/2025, 8:30 AMadorable-motherboard-7452
10/09/2025, 9:59 PMcold-alarm-37505
10/09/2025, 7:34 PMproud-controller-31469
10/09/2025, 4:44 PMquaint-machine-48009
10/09/2025, 2:52 PMloud-crowd-60573
10/08/2025, 6:45 PMproud-cpu-87812
10/08/2025, 6:25 PMproud-controller-31469
10/08/2025, 3:37 PMTypingIndicator
appears to be always active for every chatbot using this version. This happens regardless of whether the bot is actually ātypingā or not.
In the v3.2 update, the TypingIndicator behaved as expected, it only appeared while the bot was processing or sending a message. However, after the update, the indicator remains visible at all times, which can be confusing for end users.
Unfortunately, we cannot switch to 3.2 because our customer has seen this Proactive Message and reeeaally wants to keep it š„²
Does anyone else have this problem?
Best regards,
sq2-ls
https://cdn.discordapp.com/attachments/1425507426421047336/1425507426613858354/image.png?ex=68e7d6bf&is=68e6853f&hm=2c4c2b39e567220f4a2f2c4d05c22ba4d11656c7948a605957dd1e6a8a0eab4a&bulky-kitchen-40723
10/08/2025, 2:44 PMpowerful-restaurant-49993
10/08/2025, 1:48 PM