Missing boolean argument in advanced website

Hi @nayelyz ,

I added a third argument yesterday to a custom capability, it’s an optional boolean that works as expected with Rules API but it’s not displaying in the website.

It was around 30 hours ago so I guess it’s not a cache issue. There’s actually space for it so the website knows there are three arguments, but the control is not there as you can see in the picture.

It’s super low-priority since it works and probably nobody is going to use the AWA other than for testing. Thanks!