Objective: attaching conversation history in the body of a post request to an api call Issue: Script screen is of the script inside the Execute code of the llm block

messages

is undefined in the logs, which is assigned the value of

event.state.session.fullHistory

Solutions attempted: 1. removing trigger and leaving only the conversation start as the only entry point 2. replacing

event.state.session.fullHistory

with

conversation.SummaryAgent.transcript

, which is also undefined 3. Verified

event.state.session.fullHistory

is still working with a another previously published bot.

where do you have a capture card in this flow?

There is no capture card

to be honest i really don't know what the behavior of this bot should be / why it's organized this way. mind sharing what the bot / convo behavior is supposed to be?

I'll try that, this bot's purpose is essentially to use botpress as a ready made front-end widget for an existing conversaton api using gpt4, the post request endpoint provides the next assistant message

awesome. by the way you can access that variable and more by looking at the logs in the debugger window of the studio. can copy the path there directly to by clicking on the clipboard that pops up when you hover

perfect, thanks for the info

don't believe we have documentation on all the variables that you see in the JSON, but here are some docs that cover variables more broadly: https://botpress.com/docs/cloud/studio/variables/

Ok I'll figure it out then, because it's not clear how each entry in the history can vary, such as what each key means, and what are the different possible values for the keys, and which keys can appear

yes, there's work to be done to improve that part of the documentation