Hi there,
I don't know if it's expected behavior, but to me it looks like a bug.
If I have an "insert" query, it gets triggered correctly only by an explicit event, such as a button click. But if the same query contains an unknown parameter to be used by a JS Query with AdditionalScope, it gets triggered also by any other parameter change.
In the video, there are the two behaviors: the first part is the correct one, and the second part is the issue:
Is it an intended behaviour?
Thanks
Hello @abusedmedia!
Thank you for reporting this and sharing the video.
I tested this out and confirmed that the console does report error messages on every input change made to variables being tracked via the change log if one of the variables that are query inputs is not set up correctly.
I checked the 'Timeline' tab of the console and it appears that the query is not being triggered, just that the console is flashing an error to the user, to let them know that there is going to be an failed query error if/when they run it due to the input param not being set up correctly.
Once I did run the query(and have it fail) it seems that the error on keystroke goes away and is replaced by an error in the query editor and a query failed error message in the console.
Definitely confusing as the console will also show query run success/fail messages as well 
so it seems to be intended behavior.