In one particular case I still remember, a batch job I had set up had failed to run, and an entire department couldn't do their work properly the next day; during the "no literal sorry" year!
Instead of just saying "sorry" and being done, instead I was forced to come up with something more:
* "Oh no, that's terrible! We were anticipating this issue due to <reasons> and were already partially mitigating it"
* "Additional QA will likely lead to diminishing returns, but we can still add extra testing time to our daily batch update, at least it can't hurt"
* "Did you know your sysadmins can manually continue the job if this occurs? Send one of them over and I'll show them how!"
Apologizing 'properly' with or without the word "sorry" is hard, but can be done. You need to show that
a) you are aware of the problem/mistake and recognize it.
b) you are acting to prevent the problem from happening again.
c) you are (willing to) engage with the other party and empower them where possible.
* they agreed to let us to continue writing batch jobs the way were were doing, and even gave us more complex tasks.
* They sent over a sysadmin to learn how to work with our scripts.
I don't have an exact duplicate scenario in which I only said "sorry"; but I think we can assume that it would have been rather less likely for the above to happen if no-one had explicitly mentioned them.
Concilliatory actions without admission are not apologies, they are just a way to have your cake and eat it too. Abusing someone and then getting them to still deal with you after. It's even a brainwashing and abuse tactic, following abuse with kindness.
There was some article a while back that said '"Do you want to go to the store?" is not "I apologize"'