Business-blocking bug that has appeared recently. I haven't made any changes/published in ~20 days, everything was working and broke recently, due to changes not on the bot-side. Please help ASAP. I have a node who's job is to set 'date' and 'customer name' as strings to two conversation variables, then route to another workflow. The logs show two 'Mutate Property' with the correct values, but the event logger doesn't show these values changing, and print log later on shows these values empty/null. Additionally, I noticed that the Event Logger shows all variables as either 'User' or 'Workflow'. So my conversation variables are actually showing up as 'workflow' variables, which might explain why their values got lost when switching workflows? or not set at all... I have attached sreenshots that show the values of the variables throughout the flow. The variables are enabled for 'allow write access' in the autonomous node. I have even tried removing them, adding them back, recreating the node.... Please help, this is blocking our customer's operations. https://cdn.discordapp.com/attachments/1457798877523607563/1457798878198763684/Screenshot_2026-01-05_at_7.05.44_PM.png?ex=697ba301&is=697a5181&hm=07a26ddb74de5b44424fb26d0605a9000515aa9baa4a131fa338be7b80b7a705& https://cdn.discordapp.com/attachments/1457798877523607563/1457798878769451050/Screenshot_2026-01-05_at_7.05.57_PM.png?ex=697ba301&is=697a5181&hm=4a6e8aa5ac9dce23b80a8aebeddb87bda284afdc18b42f9bc7aa94dbb844b47c& https://cdn.discordapp.com/attachments/1457798877523607563/1457798879679479828/Screenshot_2026-01-05_at_7.06.16_PM.png?ex=697ba301&is=697a5181&hm=1931807efad91cf94efabe66270cdf6e0f376b887c451f8fe5c4c7a8b9ddffb9& https://cdn.discordapp.com/attachments/1457798877523607563/1457798880128143509/Screenshot_2026-01-05_at_7.07.11_PM.png?ex=697ba301&is=697a5181&hm=c063a3b796b75fd5deffa2c1becee42bedfeaed48a8a47629af44f644e8a0252&

Yeah, that’s super frustrating, especially when nothing changed on your side and it suddenly breaks. From what you’re showing, this really looks like a scope issue: the values are being set, but they’re treated as workflow variables, so they get lost when you jump to another workflow. That would explain why the mutation logs look correct, but later logs show them as empty. I’d double-check where those variables are actually defined (conversation vs workflow) and how the workflow transition works. Quick check: are you using “Go to workflow” or “Call workflow / return”, and where are those variables created? @bored-wolf-92614

Hi @delightful-carpenter-23804 thank you for jumping on this so quickly. Not sure I understand what you mean by 'where these variables are defined' ? To my knowledge, the variables are defined all in the same place (bottom-left in the studio, as seen in screenshot). The variables are definitely set as 'conversation' variables. As fro the workflow transitions, they are being called from an autonomous node that is the one that sets the variables. The card inspector shows 'Execute workflow' I'll also point out that this is happening across two separate bots, both of which used to work with the current configuration. https://cdn.discordapp.com/attachments/1457798877523607563/1457837034092761129/Screenshot_2026-01-05_at_9.39.49_PM.png?ex=695d740a&is=695c228a&hm=add505d2e7cc5373a8205d25afc62107c8c50e251fd447efdcfbdd4339052bba& https://cdn.discordapp.com/attachments/1457798877523607563/1457837034424242320/Screenshot_2026-01-05_at_9.43.22_PM.png?ex=695d740a&is=695c228a&hm=f240219ee4e6f58fcef7e9338680dcd047cc89d3d7cbca557cecd558a9fbe72f& https://cdn.discordapp.com/attachments/1457798877523607563/1457837034692415663/Screenshot_2026-01-05_at_9.43.29_PM.png?ex=695d740a&is=695c228a&hm=26e146f17edd879b98a70c9551facf632d309c4dbb3ef6d2c10506c7c8a2a1f1&

Got it, I see where the confusion is coming from, and you’re not wrong to question it 👍 When I say “where the variables are defined”, I don’t just mean where they appear in the Variables panel. In Botpress, variables can look like conversation variables in the UI, but their effective scope at runtime depends on how they’re written to and how workflows are executed. In your case, the autonomous node is executing another workflow, not calling it with shared context. When that happens, Botpress often treats the data written inside that node as workflow-scoped, even if the variable itself is marked as “conversation” in the studio. That’s why you see correct “property mutation” logs, but the Event Logger and later nodes show empty values the context is getting reset on workflow execution. This also explains why it suddenly broke across multiple bots: a platform/runtime change can alter how context is passed between workflows without any bot-side changes. If you want, I’m happy to jump in and trace the variable lifecycle end-to-end (mutation → workflow execution → downstream access) and fix this properly, it’s a classic Botpress edge case, not a mistake on your side. @bored-wolf-92614

@delightful-carpenter-23804 thank you for explanation. Having the variable scope vary like that seems counterintuitive, and conflicting with botpress docs. But i appreciate the explanation. I would appreciate any help with this, happy to give you access. Just let me know what you need from me.

Totally fair reaction, I agree it’s counterintuitive and doesn’t line up with how the docs read. Happy to help dig into this properly. The fastest way would be to look at it directly and trace the variable flow across workflows. You can give me temporary access, or we can do a quick screenshare if that’s easier. Let’s continue this in D..M so we can align on access, timing, and how I’ll walk through the fix step by step. @bored-wolf-92614

Hey guys, I THINK I experience also something like that. My conversation vars do not set the values I need with AI Tasks in some workflows. Is there a best practise for this?

Have you allowed write access to the conversation variables in the autonomous node? https://cdn.discordapp.com/attachments/1457798877523607563/1458388517829869660/image.png?ex=695f75a6&is=695e2426&hm=0dc43af189b0d0c05b6671b4f9c3cc3d33ec055c67dfe37ac29199909d32e0ed&

Yes, both variables have write access. I can see in the logs how the 'property mutation' changes the values. The issue seems to be with the Autonomous Node runtime not initializing variable scopes correctly when executing secondary workflows. I've been able to replicate the issue with different variable scopes (conversation and workflow), and in different bots. I'll also point out that the issue appeared recently, with no changes to the bot, pointing towards a regression brought by botpress runtime updates. Luckily I haven't published our production bot, which is still working, but when testing in the studio the issue is happening consistently. Same in our published staging bot. Please, can someone in the Botpress team take a look at this? https://cdn.discordapp.com/attachments/1457798877523607563/1458514501354917929/Screenshot_2026-01-07_at_6.32.27_PM.png?ex=695feafb&is=695e997b&hm=f687a388cd067c10661cf15407cdf32dc38b75fb0f714d9b0921bd8af0c183b4&