# See payload and custom error messages in exalate support logs

**URL:** <https://community.exalate.com/t/see-payload-and-custom-error-messages-in-exalate-support-logs/5616>\
**Category:** General Questions\
**Tags:** exalate, migrated\_question\
**Created:** [November 4, 2024, 8:16am UTC](https://community.exalate.com/t/see-payload-and-custom-error-messages-in-exalate-support-logs/5616 "2024-11-04T08:16:49Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![xl8bot](https://dub1.discourse-cdn.com/flex018/user_avatar/community.exalate.com/xl8bot/32/324_2.png) [@xl8bot](https://community.exalate.com/u/xl8bot)\
**Post date:** [November 4, 2024, 8:16am UTC](https://community.exalate.com/t/see-payload-and-custom-error-messages-in-exalate-support-logs/5616/1 "2024-11-04T08:16:49Z")

</div>

_Originally asked by Sandra Campbell on 25 October 2023 [(original question)](https://oldcommunity.exalate.com/questions/95585296)_

* * *

Does anyone know if it’s possible to use the support logs to

- view the payload
- show custom error messages

Would help in diagnosing issues, understand what’s happening so we can refine our processes.

We’ve been using the debug function in the code, but it would be helpful to include error messages that do not stop the code and let it run through to the end.

Needed for Zendesk and Jira On Prem.

thanks, Sandra

* * *

---

<div class="post-metadata">

**Author:** ![xl8bot](https://dub1.discourse-cdn.com/flex018/user_avatar/community.exalate.com/xl8bot/32/324_2.png) [@xl8bot](https://community.exalate.com/u/xl8bot)\
**Post date:** [November 4, 2024, 8:16am UTC](https://community.exalate.com/t/see-payload-and-custom-error-messages-in-exalate-support-logs/5616/2 "2024-11-04T08:16:50Z")

</div>

_Answer by Mathieu Lepoutre on 30 October 2023_

Hi Sandra

It is indeed possible to generate and view custom error messages in Exalate for Zendesk and Jira On Premise. You can use the ‘debug.error’ function to create custom error messages in your script which could further help in diagnosing issues. They could give insights about the values passed in a replica, for instance.

This function helps to raise an IssueTrackerException error with the value of the field which is not syncing.

For Example:

Put this in the incoming sync.

```auto
debug.error("the orignal estimate is replica.'Original Estimate' ${replica.'Original Estimate'}")

```

You can also use log.info() on Jira OP and then the logs will be generated in the log folder in the server Exalate is installed upon.

Some more documentation: [https://docs.exalate.com/docs/debugging-sync-scripts-on-exalate](https://docs.exalate.com/docs/debugging-sync-scripts-on-exalate)

[https://docs.exalate.com/docs/debughelper-in-script-helpers](https://docs.exalate.com/docs/debughelper-in-script-helpers)

Thank you.

Kind regards,  
Mathieu Lepoutre

* * *