Unofficial archive. This is a read-only, community-run archive of the Apple Support Community. It is not affiliated with or endorsed by Apple Inc.

Yellow triangle error in Final Cut Pro library

Unfortunately, I've run into a regular error again today. Just as I go to export the final deliverable for a client my main project gets a yellow triangle/! Error… There is nothing missing in the library, nothing missing on the timeline, and nothing amiss from what I can see…


I cannot understand why the Final Cut Pro team cannot add a section in the library inspector to tell us what and where the error is coming from!?! Obviously, FCP is seeing an error, why not just tell us what it is! It would make it infinitely faster to fix. I'm left scratching my head. I don't know if I should just ignore it and export… This is a very long video, 45 minutes… Having to review it every time this error appears is extremely time-consuming.


Any ideas?




[Re-Titled by Moderator]

4 replies

I've tried similar solutions lick copy and pasting the Project with success. Another thing to try is to make a compound clip of the entire timeline and then make a new project using that compound clip. Agreed that it is very odd. I have tracked down the offending issue by copy/pasting the entire clip into a new timeline for safety sake, then deleting half of it and attempting to export, knowing if that works it's in the other half...on at least one occasion it was a tiny bit of transition that somehow got left between clips and was virtually invisible until the timeline was blow up for close inspection. It's def an issue that FCP should seek to solve so we can find the problem more easily.

Maybe the word "missing" is not exactly what you need to search for.

Clear the search text, and go through the index. Is there any yellow warning there?

Try this: in the problem project, Command-A (select all), then Command-C (copy)

Make a new project with the same settings, and Command-V (paste)


Does the new project show any errors? Does it export?

Tried that, but nothing showed any yellow errors in the index.