We have also experienced this (with other types of connections). IMO, this is a big design flaw in the deployment process. I’m disappointed by the fact that the deployer provides variable substitution on the one hand and on the other hand does not substitute the values before starting the newly deployed component (but rather tries to start it with the “source” values and only then changes values). We tried to solve this via SAG support but to no avail. Bad and sad IMO.
Has anyone solved this in a pleasant way? How?