After investigation, it turns out that the root cause is the presence of a special character (>) in the query_builder table. Working with the team to figure out how to resolve.