... an update ... I was not able to recreate this scenario in our TEST environment ... in other words everything worked correctly with the job acting as I ran...
ok I have an update on this first off when we view the "Running Packages" folder in SSMS this also lists packages that are NOT running on the current SSIS...