During the execution of a package link, I am seeing work status warnings in a problematic package manifest themselves in the work status failure of a later package. The latter package runs successfully on it's own, as a stand alone package, with identical prompts. It also runs successfully in the package link once the work status issue in the problematic package is fixed.
Can anyone explain that technically? All of the packages are using script or standard business rules.
Thanks,
Tim