Thanks Vidhya but, If I am starting the job with sp_start_job I don't see how he "on error" in the SSIS package will help me.

I figure I can query the sysjobhistory table to determine the last execution status for that job, however, this seems like a problem that lots of you SQL Experts would have run into in the past and I was wondering if there was a cleaner/ better way to do this that I am not thinking of.

Thanks