Updating a custom capability

Hi,
Just checking, When a custom capability is updated using the CLI, this is not immediately seen by edge drivers. In other words we have to rename the capability and create a new one. Is this correct? Will it always be like this?

I just have a simple capability with just a command, and I had a typo so wanted to update., No presentation or translation involved

Thanks

I’ve had better luck updating them in the past few months. I think a lot of the caching issues have improved, but I still hit some weird snags. I’ve found that changing the profile’s component labels can shake the caching issues loose. I still use throwaway capability names initially though.

What are you updating that doesn’t impact your presentation and translation?

It was my initial attempt, I had the command attribute wrong, the driver failed. I did an update and tried again it didnt work, so I created a new capability and it worked