Can't scroll params list when editing an agent leading to params being cut-off

Are there any known workaround to this? Thanks!

Hi @DavidD, I was able to repro this so I went ahead and created a bug report for you. You can edit your params from outside of the "edit function" screen, but you can't input example values for testing out those particular params from the edit function screen.

If you really want to test something out temporarily and don't mind doing something hacky in the meantime, you could inspect the page and modify the css of the block (its class is _blockBodyContainer_1w20e_50) to have overflow: scroll;, which will allow you to scroll through the params and then edit the example values.

Otherwise I'll let you know how the bug fix goes!

thanks @Mike_M ! fortunately, I was able to delete some of the example values and make the existing lines shorter temporarily to edit the item I wanted to but wanted to flag as I’m sure its only a matter of time before I add more params!

Thanks for the quick response!

1 Like

No problem! Also, just coming back to this after seeing a different issue with another customer. I have seen people use 1 parameter instead and have it be an object with multiple keys. ex:

options: {
    param1: "value1",
    param2: "value2",
    ...
    param14: "value14"
}

An interesting workaround but this would make it more difficult for the agent as it would have less context, no?

I think as long as you're clear in your instructions on how the object should be defined, the agent will still ultimately see the same information. I tested it out myself and it worked out, but if it would require too much refactoring I wouldn't worry about it!

1 Like