Error preventing library action output

I’m adding a new target to a working app, and moving from a maria db, to a managed db at digital ocean using MySQL 8. The connection is working–I can read/write data, however the insert identity is not being returned in the app, thus breaking things down.

Node docker target.

Anybody experience this or have ideas?

Probably not very helpful, but I don’t think it’s a MySQL 8 issue specifically. The last inserted id is working fine - at least with PHP and not using Docker.

Ya, I’m more thinking it has to do with the DO managed database that is being used.

All my tests in new projects work, including with the managed db, so it must be something in my project. It’s gonna be one of the days. :rofl:

2 Likes

Okay, closing this out…weird stuff.

Inside a Try/Catch, several actions were successfully running, except one at the end. If that generated an error, the output from other library actions was not available to downstream actions.

I’m just fixing the error and moving forward for now.