Job Agent - Runs Without Errors, But Against Test DB

I've got a very simple package that truncates some rows from a table. The packages utilizes configurations as described in a post I made on this forum yesterday http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=3062343&SiteID=1.

When the package is deployed and installed on the prod server, it runs successfully from the Execute Package Utility, utilizing the configurations as expected, removing the rows from the target table.

When the package is run from the SQL Agent on prod, it completes successfully without errors, but the rows in the prod table remain. On the "Data Source" tab in the job, the correct connection string shows pointing at the prod database (picked up from a config file on the prod server).

Curiously, the job appears to run the truncate against the test db table - I tested this by putting rows in the target tables on both test and prod. When the package is run from SQL Agent, the test rows are removed. When run from the Execute Package Utility on prod, the prod rows are removed. Huh?

Again, the Data Source tab in the Job on prod shows the prod db connection string and the package removes the rows correctly from the prod table when run from the Execute Package Utility on prod.

Does anyone have any thoughts on this behavior when using the Job Agent to execute a package?

Thanks!

Jamie Pick