I recently got bit by this bug, but the LF Capture Engine in QF has 2 ways to retrieve entries; Basic Retrieval, and Search for Entries. If you choose Basic Retrieval, and select any fields in the criteria, those fields are available as tokens in the token shortcut menus. If you change the capture method from Basic Retrieval to Search for Entries, the session is still able to read the fields of the source entry, but anywhere the tokens %(Field.FieldName) are in the QF session, they're now underlined in red, even though the field data gets retrieved.

I would like QuickFields to either let me choose from all of my fields in the source repository as tokens, or allow me to specify which fields I want the session to retrieve from both types of Capture Engine searches; not just the Basic Retrieval. The capture engine should work a lot like LF Workflow's "Search Repository" action, where you can specify (at the very least) which fields to retrieve, and maybe even an option to pick up some of the additional properties metadata (things like Page Count, Created By, Has Image, etc.).

Right now, I'd be happy if QF Designer's tokens were just aware of the fields I'm reading data out of when I have to use a search query to feed LF Capture Engine; it's like someone just copied the top half of the Search Repository activity from Workflow, and left out the important half.

I've included photos showing the exact same QF session, one where I've configured it to use a basic retrieval; and the field tokens work. The other photo uses a search for entries query, and the field tokens are (underlined to appear) broken. Like I said, the tokens still get populated, but QF Designer acts like the tokens are wrong.