I experience this all the time and UX is absolutely one of culprits here. The workaround works, but UI doesn't nudge you to adjust the value, it just throws an opaque error. It's so obvious to me that even such a simple thing as saying "Try smaller radius" would make things more obvious, or even better - have a button in that error to "Set radius to largest valid". Saying that "but it's cause by OpenCascade" is a thought-stopping cop out. If there's a manual workaround trick, you can always integrate that into UI, but not doing so is a choice.
rounce|8 days ago
The workaround mentioned isn't a magic solution, it fails in a bunch of more complex cases too. Chamfers are a complicated operation and predicting valid values across of the operation in order to set a maximum value is, as far as I'm aware, in a similar region of difficulty. It would also be unfeasible in many cases to attempt the actual operation across a wide range of values. It's not so much a choice as just being hard to do.