# Debugging a Script in ConfigureTransform

**URL:** <https://forum.inductiveautomation.com/t/debugging-a-script-in-configuretransform/32539>\
**Category:** Ignition\
**Created:** [February 24, 2020, 1:21pm UTC](https://forum.inductiveautomation.com/t/debugging-a-script-in-configuretransform/32539 "2020-02-24T13:21:23Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jorgeibesi](https://avatars.discourse-cdn.com/v4/letter/j/ba9def/32.png) [@Jorgeibesi](https://forum.inductiveautomation.com/u/Jorgeibesi)\
**Post date:** [February 24, 2020, 1:21pm UTC](https://forum.inductiveautomation.com/t/debugging-a-script-in-configuretransform/32539/1 "2020-02-24T13:21:23Z")

</div>

Hello, How I can show messages in my console to track the flow execution of my script in Configure Transform. I tried several ways, but doesn’t work.

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/2X/4/465b2758e821b137ded370eb54a81aa159127da0.png)

---

<div class="post-metadata">

**Author:** ![kirsten.chambers](https://avatars.discourse-cdn.com/v4/letter/k/48db29/32.png) [@kirsten.chambers](https://forum.inductiveautomation.com/u/kirsten.chambers)\
**Post date:** [February 24, 2020, 3:10pm UTC](https://forum.inductiveautomation.com/t/debugging-a-script-in-configuretransform/32539/2 "2020-02-24T15:10:48Z")

</div>

The most straightforward way to debug is using `system.perspective.print()` which will print messages into your designer’s console (Ctrl+Shift+C).

Logging like you’ve done in your screenshot is also possible, but then you have to go to your gateway in your web browser–\> Status–\> and click on Logs under Diagnostics to see the actual logging taking place, which I don’t recommend over the ease of using the print function for debugging purposes.

---

<div class="post-metadata">

**Author:** ![cmallonee](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/cmallonee/32/6416_2.png) [@cmallonee](https://forum.inductiveautomation.com/u/cmallonee)\
**Post date:** [February 24, 2020, 3:29pm UTC](https://forum.inductiveautomation.com/t/debugging-a-script-in-configuretransform/32539/3 "2020-02-24T15:29:58Z")

</div>

What @kirsten.chambers posted is indeed the recommended way to debug Perspective scripts, but you need to make sure that you remove such lines before sending to production as the `system.perspective.print` function also prints to the browser’s development console. This means that anything you log in a given session with `system.perspective.print` could be viewed by the user of that session as long as they know how to open a browser’s development tools.

---

<div class="post-metadata">

**Author:** ![Jorgeibesi](https://avatars.discourse-cdn.com/v4/letter/j/ba9def/32.png) [@Jorgeibesi](https://forum.inductiveautomation.com/u/Jorgeibesi)\
**Post date:** [February 24, 2020, 3:55pm UTC](https://forum.inductiveautomation.com/t/debugging-a-script-in-configuretransform/32539/4 "2020-02-24T15:55:16Z")

</div>

> [@kirsten.chambers](#):
>
> system.perspective.print()

Thank very much to both.