# How to find where and error is ?

**URL:** <https://community.ofelia.com/t/how-to-find-where-and-error-is/5667>\
**Category:** Q&A\
**Created:** [17 February 2015 10:07 UTC](https://community.ofelia.com/t/how-to-find-where-and-error-is/5667 "2015-02-17T10:07:34Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![yannick.lombardi](https://avatars.discourse-cdn.com/v4/letter/y/8e8cbc/32.png) [@yannick.lombardi](https://community.ofelia.com/u/yannick.lombardi)\
**Post date:** [17 February 2015 10:07 UTC](https://community.ofelia.com/t/how-to-find-where-and-error-is/5667/1 "2015-02-17T10:07:34Z")

</div>

Hi.

On Bonita Studio, when I click on “Run” the studio run the process Validation.  
An error message say “Some errors have been found in the diagramProcess”.  
I click on “See details”. It open the “Validation status” tab.  
This tab is empty.  
I check the “Validation status” tab of all my subprocess, but they are all empty.

How can I see where the validation found an error ?

---

<div class="post-metadata">

**Author:** ![marcy.ira](https://avatars.discourse-cdn.com/v4/letter/m/3d9bf3/32.png) [@marcy.ira](https://community.ofelia.com/u/marcy.ira)\
**Post date:** [17 February 2015 12:04 UTC](https://community.ofelia.com/t/how-to-find-where-and-error-is/5667/2 "2015-02-17T12:04:51Z")

</div>

Check Validation Status by clicking Refresh. Check diagram for any X on task or gatways.  
Go to Bonita BPM Engine Log and check what is written

---

<div class="post-metadata">

**Author:** ![yannick.lombardi](https://avatars.discourse-cdn.com/v4/letter/y/8e8cbc/32.png) [@yannick.lombardi](https://community.ofelia.com/u/yannick.lombardi)\
**Post date:** [17 February 2015 12:59 UTC](https://community.ofelia.com/t/how-to-find-where-and-error-is/5667/3 "2015-02-17T12:59:48Z")

</div>

Validation Status is empty even after clicking on Refresh. I try this in every Process.  
I have no X anywhere.  
Bonita BPM Engine Log are empty too.

I restart Bonita Studio and try to run the process again. Now it works fine. The invisible error vanished.

I don’t know what happened. Maybe a bug but now it works.