# View All Errors / Project Cleanup

**URL:** <https://forum.inductiveautomation.com/t/view-all-errors-project-cleanup/59362>\
**Category:** Ignition\
**Tags:** perspective\
**Created:** [May 9, 2022, 3:38pm UTC](https://forum.inductiveautomation.com/t/view-all-errors-project-cleanup/59362 "2022-05-09T15:38:11Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![MattEbert94](https://avatars.discourse-cdn.com/v4/letter/m/779978/32.png) [@MattEbert94](https://forum.inductiveautomation.com/u/MattEbert94)\
**Post date:** [May 9, 2022, 3:38pm UTC](https://forum.inductiveautomation.com/t/view-all-errors-project-cleanup/59362/1 "2022-05-09T15:38:11Z")

</div>

I’ve encountered a few instances where I’ll open up a component only to find that it has a property error related to something that wasn’t the case when I first created the component. For instance, maybe I moved a component into a different container and the address/reference to that component broke.

Is there any way to do a full project search for any errors/warnings? It seems that without clicking into each component, I would never be able to find those.

Thanks!

---

<div class="post-metadata">

**Author:** ![apalas](https://avatars.discourse-cdn.com/v4/letter/a/e47774/32.png) [@apalas](https://forum.inductiveautomation.com/u/apalas)\
**Post date:** [May 10, 2022, 9:24pm UTC](https://forum.inductiveautomation.com/t/view-all-errors-project-cleanup/59362/2 "2022-05-10T21:24:51Z")

</div>

Hi Matt,

Component / property errors aren’t visible to any search features that we currently provide unfortunately. They typically appear the moment you open up a specific window that contains it since it’s an error caused by the execution of a binding, script, etc. You will need to keep an eye out for errors that appear as windows are being viewed similar to how you would execute a script and keep an eye out for compile and runtime errors.