Okay, this is something I was trying to explain earlier but didn’t do a good job of it. You might wish to follow the tutorial through Step 6, to where it leads you in Part II, as this concept and how to make use of it is described there. Scrivener’s folders are really actually text files. They can contain text within them just like “files” can. Everything in your Draft is technically a file you can type into. Now, most people don’t type text directly into their folders, mainly because the software presents folders as corkboards by default, but if you turn the corkboard off on a folder, you will see a text editor, and if you type into it, the folder icon will change to indicate that it contains text.
Your folders, very likely, are empty of text, so when you click on them and load them as files they will be empty. That doesn’t mean the link is broken, it means the text editor hasn’t been used yet, that’s all.
The Reveal in Binder command is used from within any text editor (even QuickReference windows) to reveal that item in the Binder. It sounds like you highlighted the text of some hyperlink in your text editor and used the command, but it’s not paying any attention to your selection. Since this command targets what you have in the text editor, it will reveal the ToC in the Binder, the file you highlighted the link from. You have to click on the link, and use the Reveal command from the empty editor you are curious about. If the Binder highlights the folder you selected, then the link is not broken. By the way a broken link gives you a warning when you click on it, not an empty document.
All right, that aside, I need some clarification. At the beginning of the thread you mentioned that when you compile to PDF, you see <$p> in the output. In this last set of posts however, you are saying that when you compile to PDF, you see “??”. Up until this point in the thread, I’ve been working under the assumption that you see <$p> in the PDF. What has changed with what you are doing, if the result has changed?
That wouldn’t ordinarily be necessary unless your folders are completely absent in the output. What is very common is that people use folders to print a chapter heading and generate a page break. That is how our templates work out of the box. Are you doing something different? If the folder is just serving as an “invisible” divider for your eyes only in the Binder, then it is not a suitable target for the end output’s table of contents, since the target doesn’t “exist” in the compiled document.