All of a sudden the past week, our jobs have stopped working correctly. Not sure if any auto updates have come down, but the jobs affected have not been changed at all.

The issues we are having are when we run jobs with context variables that have the Prompt tick box ticked.

Normally with the tick box ticked, when the job runs, it will prompt you with the defaults for these variables, allowing you to overwrite them at runtime. We use this functionality quite extensively, especially with database connection contexts to allow us to specify the server and database name we wish to run the job against.

This has been working perfectly fine, but in the last week, this has stopped working correctly.

Here's an example.

As you can see from the screenshot, this job is setup with a database connection context, with the tick box ticked on prompts for the some of the parameters, including the database name.

In the screenshot, you can see the database name is set to "Transform_DB_0408"

This is how the tDBConnection_1 component is set up. As you can see it is being told to use this context.

From the below screenshot, you can see that the tDBRow_1 component is being told to use and existing connection, and the connection it should use is the details in the tDBConnection_1 component.

When I run this job, I get the expected prompts:

As you can see I am changing the default database name to a different database. So the job should now use this database.

However, it does not, and errors. The error is suggesting it is trying to connect to the default database "Transform_DB_0408".

It has never done this before, and I have no idea why this has all of a sudden started happening, but it is very annoying and causing us all sorts of issues.

Does anybody have any ideas at all?

Thanks

Steve