# Extend debugging/datapoint functionality to failing transformers

**URL:** <https://forum.alumio.com/t/extend-debugging-datapoint-functionality-to-failing-transformers/445>\
**Category:** Feature Requests\
**Tags:** data-transformer\
**Created:** [February 20, 2023, 8:30am UTC](https://forum.alumio.com/t/extend-debugging-datapoint-functionality-to-failing-transformers/445 "2023-02-20T08:30:56Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![koen.schoute](https://forum.alumio.com/letter_avatar_proxy/v4/letter/k/3ab097/32.png) [@koen.schoute](https://forum.alumio.com/u/koen.schoute)\
**Post date:** [February 20, 2023, 9:56am UTC](https://forum.alumio.com/t/extend-debugging-datapoint-functionality-to-failing-transformers/445/3 "2023-02-20T09:56:59Z")

</div>

Hi Roland,

Thank you for your reply. The original functionality is described here: [Datapoints (breakpoints) in transformer for debugging](https://forum.alumio.com/t/datapoints-breakpoints-in-transformer-for-debugging/415) .

However, when a data/entity transformer fails, the datapoints/breakpoints do not get updated with the data of the failed run. This can be very useful in determining what is going wrong.

So in summary, my request is to keep the same functionality when the entity transformer fails, Not only when the transformer succeeds. So that we can see the data until right before the error occurs.

---

_[View the full topic](https://forum.alumio.com/t/extend-debugging-datapoint-functionality-to-failing-transformers/445)._