SMTP Integration in Automations not using updated settings

:robot: Kuma (Baserow’s AI assistant): often the fastest way to get help. Try asking Kuma before posting here. Available to all SaaS users, and to self-hosted users with a connected AI model.

on

Are you using our SaaS platform (Baserow.io) or self-hosting Baserow?

SaaS

What are the exact steps to reproduce this issue?

Create an automation the sends email, perhaps triggered by an update to a table. Create a standard automation flow to iterate through all rows changed in the trigger. Create an event to send an email using a new or established SMTP integration. Test and publish the automation. Open your table and modify a row to fire the trigger. Wait for your email. Open the automation again. Modify the SMTP configuration. In my case I used an entirely different SMTP server. Save the integration. Make sure the new integration (if you have more than 1) is selected in the automation. Test and publish. Open your table, modify row and wait for email.

It will not be using the new SMTP server settings from integration update. It will be using the original settings. The only way I have found to change SMTP settings is to delete the SMTP integration, create a new one and change on all automations that use it.

Hey @danielgoad,
I haven’t been able to reproduce the issue.
Maybe I missed something. Please share with me a screencast in DM so I can replicate this on my side.

This problem was happening at the same time as the issue shown above. When the issue above was fixed, this problem resolved. Perhaps the changes I made to the smtp server was processing on one of the workers that couldn’t connect?

I will double check that it is working as it should, I don’t often change my SMTP servers, so I can’t say for certain that it is working correctly, but I will verify and let you know.

It is now working correctly. Not sure if it was tied to the previous issue or not, but I noticed them at the same time.

Okay, I’m glad to hear that it’s working. It could very well be a side effect of another bug fix.
Let me know if the problem happens again.