How many failures do you get from legitimate UI changes and how do you mitigate that from happening?

[sebastian_solidwork (Sebastian Stautz)]

I quote myself from this other thread:
https://club.ministryoftesting.com/t/what-makes-automated-tests-checks-flakey/72173/17

@sebastian_solidwork

I find “End 2 End” being done by GUI very wasteful. I know that is often a escape path for check automaters without much support for testability of the product.
Welcome to automation hell if you lack time to adapt the automation to the changes in the UI … I have been there.

In my current project we check most business logic via API. And the GUI part is more about “Does the UI works at all”, which includes the connection to the server.
The API parts needs around 1,5 hours and is quite stable in terms of check code calling the application. The GUI parts runs in around 10 minutes.

Part of the problem is sometimes the “We do our (most) automation through the GUI.”.