Skip to main content
New Participant
Nov 13, 2026 5:59 AM UTC
Question

Versioning of Inline Dynamic Resolver

Hi all,

I’ve noticed something peculiar with the versioning of an asset in Tool Studio. In particular, I am viewing a past version of a Conversational Process (CP).

This CP has a slot with a custom inline resolver strategy (definitely not a Custom Data Type). In the Input Mapping section, it was previously set to a hard-coded value e.g. floor_id: ‘”123”’. This was done by someone else who initially created the CP. I have since updated to pass the value via context-passing from the main databank.

I was able to identify the version that was before I started working on the CP and I opened that version in the editor:

However, when I edit the Resolver Strategy I am seeing the most recent changes I have made and not what I expected to see in Version 12. In the screenshot below, “data.passed_floor_id” and the Input Argument for “all_desks” should not be there as I clearly recall creating and naming these objects. The Input Mapping should have shown a hard-coded value and the Input Arguments should have been blank.

I was also able to go through a few versions older than this and still saw the newer changes that I had made.

My question is - is this a bug in the versioning system or a limitation that I should be aware of when it comes to inline resolver strategies specifically? 
 

1 reply

eberteo
Known Participant
Nov 13, 2026 6:36 AM UTC

I clearly remember seeing this one. And fixed it recreating the whole plugin. My guess it’s that the bug was somewhere in the internal cache. I fixed it by recreating the http actions, compound actions, slotters, CP, renaming every asset process as well; bc I was getting a previous saved response in the payload from the previous request compared to the updated one that my Bruno API was providing me; which didn’t make sense at all. 

linkedin.com/in/eberteo/