Hi,
I noticed something unexpected today with deployment parameters that I would like to hear others opinion on.
The situation at hand is that we have several automations running on FME Flow. In these automations an external action is present to send an email upon success. For the 'Email_To’ parameter of this email action, a deployment parameter is being used.
It thus currently looks something like this;
And then in an automation it would look like this;
Then I had this automation running, and if it gets triggered, the email is send like intended.
But now I wanted to remove one recipient of the emails. Therefore, I changed the value of the deployment parameter email_to from 'email_adress_1,email_address_2’ to 'email_adress_1’;
Now for the unexpected behaviour. I noticed that after changing the value of the email_to deployment parameter, if I would again manually trigger the (still running) automation, I noticed the email would still be send to both the email adresses, where I expected it to honor the new value of the email_to deployment parameter and just send the mail to email_adress_1.
So in the current methodology it seems that when you change the value of a deployment parameter, one also needs to redeploy (i.e. stop and restart) all automations that are using this deployment parameter for the changed value to take effect. To me that seems like a bug.
On the other hand, some of my collegues made the argument that for security/robustness perspective one can also argue that one wants to avoid automations to suddenly stop working when a deployment parameter is removed.
Curious to hear your thoughts on this.
In more practical sense; Should an automation fetch the value of a deployment parameter only at time of deployment, or should it fetch the value again every time it is triggered?
Kind regards,
Thijs
ps. running on FME Flow 2025.2.1 Build 25815 - linux-x64.