"Can't you just write an if so the failing queue kinda restarts and processes the disappearing job when the bug occurs?"

No, you dense fuck. We've been over this every time you bring up this rotten, diseased garbage of a project. The queue does not work because the project was developed with a PHP version that was already EOL at the time, in an old framework that was also EOL at the time by the way, surely because someone told the brainless intern to "just copy paste from another project and change a couple of stuff" probably (that wouldn't be you? No? You sure?) and the queue fails because of a bug with the framework itself and I am NOT going to waste my time trying to decipher what the fuck this c programmer was trying to achieve with these 1600 lines of code in a single method. Yes I've seen the flowchart. No it still makes no fucking sense.

It reads from a csv. Updates some mysterious and undocumented mongodb collections. Some mysql tables as well. It also updates some fucking text files for good measure too. Text files. Oh, and It also connects to a third party API and does even more changes based on the responses. There are PHP IIFEs all over the place. Property names so short you'd think we were trying to save up on space but that clearly isn't the case, is it?

And am I expected to somehow unfuck this while babysitting the rest of the devs, write some fucking documents so that you can justify asking for more money because of your own technical debt fuckups, handle nearly all deployments, unfuck more doomed projects that were never stable or documented?

Can't wait to leave this shithole of a company. You can't attract talent. You can't retain talent and you actually made all the competent devs quit with your bullshit.

Now I'm the only senior, tech lead, devops, sysadmin and you want me to take on pm duties as well since the other pm left? Fuck. Right. Off.