Thanks , the issue is pretty obvious once I actually see your code. You’re not setting a custom savepoint at all, nor is the issue with a query column identifier as I first thought. This is an issue with the savepoint names that Boxlang generates for nested transactions:

I’ll have a fix pushed up shortly.

I guess I found the issue:

And in getPublishJobID():

So we have nested transactions, which is no problem with ACF and Lucee but causes “Failed to set savepoint” errors in Boxlang.

There’s no separate log file for these - they will log to standard out, I believe. In CommandBox, you get this by running server log --follow.

By “share the query”, I was confusing - my bad. I meant share the code which builds the query, including the full transaction{} block.

If I remove or comment the cftransaction tag, the error message is gone

I can’t find the query in the logs, my server runs with debug enabled. Which logfile is this?

If you run your server with debug mode enabled, you will see this SQL log prior to every query build:

Building new PendingQuery from SQL: [{}] and options: [{}]

Please share the relevant log - i.e., the matching log line immediately prior to the savepoint error.