Hey @Jon ,
It seems to happen once you either trigger a node that uses the database credentials or test the connection from credentials, it will succeed the first time and then it will through the error message if you test the connection again. For the workflow, this is just a test workflow we have, the input of the SELECT node is the manual trigger, not really consuming anything from the previous node. Let me know if that answers your question.
Regards,
JC
Hey @jespinoza,
That does indeed answer it, I will see if I can get to this today before I am off for a few days.
Hey @jespinoza,
This has been fixed in the PR below (or at least it is all good with my testing), This has been reviewed and will be merged and released at some point this week.
New version [email protected] got released which includes the GitHub PR 7087.
Hi @Jon and @jan I just upgraded the workplace and everything seems to be working as expected. Thanks a lot for your support.
Regards,
Jean C
Hey @jespinoza,
That is good news, It is nice to finally have this one resolved 
That’s right, thanks a lot for all your support again. So far it has been a great learning experience.
Regards,
JC
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.