# Better failure messages **URL:** \ **Category:** Feature Requests\ **Created:** [May 8, 2019, 10:16am UTC](https://www.finalbuilder.com/forums/t/better-failure-messages/6488 "2019-05-08T10:16:03Z")\ **Posts on this page:** 1\ **Showing post:** 4
**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:** [May 9, 2019, 1:52am UTC](https://www.finalbuilder.com/forums/t/better-failure-messages/6488/4 "2019-05-09T01:52:46Z")
> [@L4ZZA](#): > > That link only sends you to the collapsible log which is not easy enough to read. We agree and have lots of plans to improve the build log, including showing an error view. Note that as of [v1.8.1.682](https://www.finalbuilder.com/downloads/continuaci/continuaci-version-history-v1.8.1) the latest error message is shown in the build log at the end of each failed action. We also have shorter term plans to add expressions which you can use to extract error messages from the log file. > [@L4ZZA](#): > > Is there a way to tell CI what name to give to the log file so that it can be associated with the build “name” instead of have them all named as “log.txt”? > The ideal solution would be to include the custom build identifier we set to the configuration variable `%BuildIdentifier%` . I’m not sure why you would need to do this. The log.txt file is already in a folder associated the build. The workspace folder is unique to the build and ends with the build number. You can use the Copy action to copy it to another folder and a Rename action to rename it. You can use the expression `$Build.BuildNumber$` in the New Name field to the Rename action to identify the build. If you put these actions under a Catch action, then they will run when the stage fails. > [@L4ZZA](#): > > Is there an API to communicate to CI via scripting language (i.e. Python, C#, Lua, etc.) We have been working on a Rest API, but this is currently on hold until we can convert the code base to .net core. You can run external programs, PowerShell scripts or FinalBuilder scripts from build actions to read and parse the log file. > [@L4ZZA](#): > > As for the update, we’re relatively small company but with slower processes than a corporate and I don’t think the update will happen any time soon… We are also a small company. Our processes are fast but with have a large feature list to implement. Note that you’ll need to upgrade to take advantage of any new features that we implement based on your requests. --- _[View the full topic](https://www.finalbuilder.com/forums/t/better-failure-messages/6488)._