When do database diagrams stop being useful in real projects?

In many projects, diagrams are very helpful at the beginning, but tend to be abandoned once the schema stabilizes and development speeds up.

From your experience, what usually causes this shift?
Is it maintenance cost, lack of trust, tooling limitations, or something else?

I’m interested in real-world reasons, especially in medium to large systems.