I would like to add something to Scott's comments. Sounds like you are fairly new to SW and you might miss something here. Note Scott is telling you how to FIND the error, but don't try to FIX the errors in the same order. Feature errors are parent-child dependent, so you work on FIXING the errors highest in the feature tree first. So as Scott says, rollback one at a time until you do not get anymore errors (you found the root cause). Then look at the last error you found - which will be the highest or first error chronologically in the tree. Most often once you debug and fix this, the rest pretty much sort themselves out (at least most of them) because that was the parent causing the the children to fail. If they don't, and you still have residual errors, you work DOWN the tree when fixing. Also as you roll back one at a time as Scott mentioned, doing a quick "What's Wrong" sometimes can be very helpful. (I only said "sometimes"! See below ***).
BTW: For Mate errors you work from the bottom up, because they are not parent-child and it is the LAST one added that causes the problems.
*** It's like the old joke... small plane - lost in fog near Seattle - gap in fog - pilot sees guy at open office window - - shouts "Where am I?" - answer "In an airplane." - pilot makes a 270 left - breaks out of the fog right on the approach path and excutes a perfect landing - passenger asks how - pilot says - "I asked for specific help - he gave a perfectly accurate but totally worthless answer so I knew it was the Microsoft office building 5 miles due north of the runway!"
John Richards Sr. Mech. Engr.
Rockwell Collins Flight Dynamics
There are only 10 types of people in the world - those who understand binary and those who don't.