In an automation script, if Settings | "Run Mode" is switched from "Test" to "Production" the connection fields within the activities in the automation are not switched as expected. Some are correctly switched from the defined test connect to the prod connection but some are not. This is only in the display.
When run, the displayed connection is not used. The original connection (as automatically applied when creating the automation) is used to run instead of the expected changed connection. This can cause confusion.
Example:
Automation first built using test settings, usera@testdb in the Automation Settings.
Review the script. All activities display the usera@testdb connection.
Run the script. All activities run under the usera@testdb connection.
Then specify usera@proddb for the production settings in the Automation Settings.
Toggle the Run Mode from "Test" to "Production".
Review the script. Not all activities will consistently display usera@proddb connection. Some will display the testdb connection.
Run the script. All activities run under the usera@testdb connection. None will run in the proddb connection.
