So I have another solution if you just add the problematic ssis package it to an already functioning sql job that contains a similar ssis package, as a second step, just not the first step, it runs fine as will

Never witnessed an ssis package that needed a emotional support ssis package to run but here we are