# Better trace for system messages

**URL:** https://www.finalbuilder.com/forums/t/better-trace-for-system-messages/7547
**Category:** Feature Requests
**Created:** [October 7, 2024, 8:00am UTC](https://www.finalbuilder.com/forums/t/better-trace-for-system-messages/7547 "2024-10-07T08:00:01Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![k3tchup](https://www.finalbuilder.com/forums/user_avatar/www.finalbuilder.com/k3tchup/32/2162_2.png) [@k3tchup](https://www.finalbuilder.com/forums/u/k3tchup)
#### Post date: [October 7, 2024, 8:00am UTC](https://www.finalbuilder.com/forums/t/better-trace-for-system-messages/7547/1 "2024-10-07T08:00:02Z")

</div>

I would like to propose a general improvement for system messages.  
Message should at least show a trace to culprit (agent, configuration, build).  
I know that there are some message already improved, but today I came across this:

 ![obraz](https://www.finalbuilder.com/forums/uploads/default/original/2X/1/15f9617d2db96e8a0d804d3bfd50d8dd06eeb428.png)  
I don’t know how to find the failing trigger.

---

<div class="post-metadata">

### Author: ![Sparky](https://www.finalbuilder.com/forums/user_avatar/www.finalbuilder.com/sparky/32/10_2.png) [@Sparky](https://www.finalbuilder.com/forums/u/Sparky)
#### Post date: [October 7, 2024, 10:50am UTC](https://www.finalbuilder.com/forums/t/better-trace-for-system-messages/7547/2 "2024-10-07T10:50:32Z")

</div>

Hi Michal,

Yes, we do try to add the configuration details, or a link where possible, to error messages. Unfortunately this sometimes gets forgotten. We will update this specific error message and related messages for the next version. Any other error messages will also be updated in due course.