The first thing to check is that we are not reading the principle too quickly, but actually reading it and absorbing the detail that’s written.
Agile processes
promote sustainable development.
The sponsors, developers, and users
should be able to maintain a constant pace indefinitely
One big push to get the thing in on time, cut corners as long as the promised date is met who cares about the quality. That was so familiar as projects failed to deliver quality and burned out the people on them.
Plan better, don't let the project run you, you should run the project. If you can deliver 6 things a week then your goal should be 6 things. You shouldn't drop to 4, or be asked to up that to 8.
This is better but partly down to some of the other principles as people work together. Where you see this not working so well you do see a lot of tech debt and poor customer satisfaction. What should you watch out for
Fixed timelines planned months in advance
Dates set by some for others
Warranty periods (you are not making shoes)
There is resistance from many to use estimation techniques but when used well they can support this principle by allowing trends to be calculated and monitored.