The new changes to Queries

I see absolutely no documentation on the changes to queries and right now my sessions are unuseable.  Multiple mainstay macro buttons used by players and myself during sessions are just flat out not working still and I have a session in 18 hours.   Do I need to now go into all of my macros and rewrite them?  What is the new syntax, where is the documentation and why couldn't we have seen this as a warning where we could have possibly gone and worked on this on the dev server first so it didn't break our live sessions so suddenly?  Can someone please explain the best course of action here?

The code was rolled back an hour or two ago. Are you still experiencing an issue? The feature was on the dev server for several weeks. The bug was mentioned in the last post on the feedback thread, and was probably missed.

I have multiple macros that are ignoring that they are queries and just spitting out the last entry in the query line, and the apply damage scriptlet that is known by many that is suppose to add a button to the group check script and apply damage to selected tokens does not do that anymore and instead just spits out the main menu of group check.  Its essentially all of my query macros that utilize html escapes that are broken.   What feature?  What is the new syntax for nesting a query in a query, I'll fix it myself if someone will show me but the wiki is followed to the T in these macros and they just simply do not work.  Also the default answer to open queries are behaving weirdly as well.  

keithcurtis said: The code was rolled back an hour or two ago. Are you still experiencing an issue? The feature was on the dev server for several weeks. The bug was mentioned in the last post on the feedback thread, and was probably missed. I use Token Action Maker and the Save and Check functions are still broken. It is at least a different error this time, which is likely some kind of progress.

Also another minor bug which is annoying is that the latest patch changed open ended queries.  Example:  MarchingOrderAPI, when you try to follow another token, it would query you with a follow distance that defaults to 0 and is selected so if you type anything it replaces the 0.  With this new borked patch, open queries like this with a default answer are no longer selecting their default answers so you have to multiselect the default answer to overwrite it with a new entry, seems like a minor issue but....its more clicks, oftentimes these scripts and queries we're making are designd to save clicks and this new behavior just makes no sense, why is it not autoselecting the default answers?