Join's bridge: "hey man, something is wrong with your DB. our app can't connect in any environment, it started after our code release last night"

"Every other app connecting is working as expected, could you rollback your release?"

"nah, that can't be it. we validated it works"

"Then why am i on an outage bridge? call me if it's still broken after you rollback"

3/16: I need a service account for $domain. I've opened a ticket with Subject: please create $account name for $domain and Description: please create $account for $Domain. I need this by 3/23.
3/21: hello?
3/23: hello?
3/28: hello?
3/30: hello?
3/30: yes, hi, is this for $domain or $differentdomain.

coming back from monday OoO to this email chain from user 1. "hey i get an error please help" 2. cc teammate 3. cc my boss. 4. cc his boss. 5. meeting between him and someone on a different team who'll 'take care of it'
Get pinged in slack before i even sit down 'please help'
"hey man, whats the error?"
'oh i get a java exception in $application_completely_unrelated_to_anything_weve_ever_worked_together_on and you've fixed errors like this for me before can you do your magic . #bro

When its saturday morning and you're on a bridge because the migration is still failing 34 hours in and the PM mentioned the vendor doc that he 'trimmed for your benefit' and replaced with his terrible doc, and you beat the original out of him and basically read off the section title "Exactly the error you got and the steps to prevent and resolve" and section 2 "big bold red letters explaining how to avoid it" and you instafix it. #wherewereyouonthursday