# How ti identify my exact issue

**URL:** <https://forum.sambapos.com/t/how-ti-identify-my-exact-issue/30404>\
**Category:** V5 Issue\
**Created:** [April 28, 2025, 1:35am UTC](https://forum.sambapos.com/t/how-ti-identify-my-exact-issue/30404 "2025-04-28T01:35:37Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Memo](https://forum.sambapos.com/user_avatar/forum.sambapos.com/memo/32/55443_2.png) [@Memo](https://forum.sambapos.com/u/Memo)\
**Post date:** [April 28, 2025, 2:52am UTC](https://forum.sambapos.com/t/how-ti-identify-my-exact-issue/30404/2 "2025-04-28T02:52:12Z")

</div>

From what I can gather looking at previous threads, it seems to be an issue with a non-existent print job.

As for what to use, you can turn on the rule debugger. Before you close the ticket, clear out the debugger, then close. Look through what events are published and what actions are fired to help you hunt down what might be executing the print job.

> [@Ticket not saved error?](https://forum.sambapos.com/t/ticket-not-saved-error/24758/2):
>
> The following solution worked from the Samba support team. thanks @Nizam! "You can check if there is a Print Job which was tried to be used by the system although it does not exist/removed in your Printing Actions. If so, you can remove/change that print job from the related action and remove that action from the related rule. (By default it is the Ticket Closing Rule however it could change depending on your configuration)"

---

_[View the full topic](https://forum.sambapos.com/t/how-ti-identify-my-exact-issue/30404)._