Can't find unresolved link

[Centauri27]

Here is a problem that has vexed me all afternoon: I am compiling my project to a PDF target. At the end of the compilation I see this error message:

"Unresolved link(s) to file: <fileName>. File may not be included in the output."

And in the "File" column, it simply shows the full path to "<fileName>" again, which seems to imply that Flare thinks <fileName> is referencing itself.

What puzzles me is that the topic for <fileName> has been tagged out of this PDF compilation and is not listed in the TOC. Similarly tagged-out files are mentioned in the "Excluded from output: <name>" messages. But for some reason Flare keeps bugging me about unresolved links to this particular file. There are only a few links coming into this file and I've verified them all.

Does anyone have any ideas why Flare is doing this?

Thanks.
Carl

[ABC_xyz]

I have the same exact problem. Anyone with a solution or hint where to look? It is attempting to link to itself, which is a file NOT INCLUDED in the TOC because it is not included in this part of the project. I've checked the xml, all files mentioned, there is nothing calling this link to itself.
Thanks for any help,
Sarah

[crdmerge]

Do you have a "Return to Top" link in there, somewhere (<a href="#">Top</a>)?


Good luck,
Leon

[helen]

I've recently had a very similar problem with Flare reporting unresolved links to itself. My file WAS linked and WAS included, however, it was a bookmark in the topic that didn't exist, once I removed the bookmark and just linked to the topic, everything was perfect. Hope this helps...

[Centauri27]

Do you have a "Return to Top" link in there, somewhere (<a href="#">Top</a>)?
Good luck,
Leon

We use "return to top" in other topics, but not in this one. The only other clue I have is that "<fileName>" was created recently, cloned from another topic. It is baffling why Flare would flag a topic that has (ostensibly) been excluded from the target.