It was late when I posted, so I’d add a little extra clarification as to how this error occurred. It’s easy in the moment to hit Return, with a new agent in mind, but actually make a note. Historically we’d a have used the inspector to add the agent query, which Tinderbox detects for use:
We can’t enter a query here as the ‘agent’ is actually a note. In fact if you select your agent-note in your demo and view the Query Inspector, i.e. as above, the code is there but the rest of the pane is grey. A good prompt, now we know, that we may have made an error.
For clarity, there is no mechanism to alter an existing note into an agent or vice-versa.
Or we might try and set—for a note—a query via Get Info. Tinderbox has this error covered too:
The way the error occurred here (the presumption of a note being an agent, was because the query was set via action code. This routes around Tinderbox’s defences. No harm is done, but the result is the simple error of using a note where an agent was expected is not caught.
If you want to check if you’ve other notes mis-purposed as agents, from v9.3.0 (and the addition of $IsAgent) you can make a agent with this query:
Here I’ve added it to my previous test doc:
Sure enough, the faux agent “Find Tasks - note” is detected.