This is a tricky one, and it sounds like the issue is with how the database connection is handled differently when you're editing versus when the script runs.
First, definitely update to the latest version...you're over a year behind, and this might already be fixed.
That error you mentioned: “login failed for user” on localhost_tedataoperationreport_connection, suggests the script is falling back to a saved or default connection that’s either broken or missing credentials. It probably works locally because you're manually reconnecting to the right database, but at runtime, it’s defaulting to something else.
To fix it, make sure your script explicitly connects to the correct database at runtime using the proper credentials. Don’t rely on any saved connections. Be sure to explicitly add Connect to ___ db step. If that old connection is still hanging around in the project, try removing or overriding it. Also, double-check that the bot runner has access to the same DB drivers, network, and permissions as your local setup. Adding a quick log step to print out the connection info at runtime can help confirm what it’s actually trying to use. Good luck!