Receiving Error in RT-Logs

Hi,

For the past few days I have been messing around with SLA’s. I managed to
get them working but ever since then (I think) I have been receiving an
error in RT-Logs.

The error message I am getting is:

Too late to safely run transaction-batch scrips! This is typically caused
by using ticket objects at the top-level of a script which uses the RT API.
Be sure to explicitly undef such ticket objects, or put them inside of a
lexical scope. at /usr/share/request-tracker4/lib/RT/Ticket.pm line 3334
during global destruction.
(/usr/share/request-tracker4/lib/RT/Ticket.pm:3334)

I do not understand why I am seeing this error. Can any one help please?

Many thanks and regards,

Aaron

View this message in context: http://requesttracker.8502.n7.nabble.com/Receiving-Error-in-RT-Logs-tp57716.html

Too late to safely run transaction-batch scrips! This is typically caused
by using ticket objects at the top-level of a script which uses the RT API.
Be sure to explicitly undef such ticket objects, or put them inside of a
lexical scope. at /usr/share/request-tracker4/lib/RT/Ticket.pm line 3334
during global destruction.
(/usr/share/request-tracker4/lib/RT/Ticket.pm:3334)

I do not understand why I am seeing this error. Can any one help please?

As it indicates, this error is caused by something keeping a ticket
around too long.

We would need to know your actual RT version, as well as custom code
you’ve written. You may also get more information if you enable
LogStackTraces at the warning level.

It’s possible this is tied to your later question where you ask about
misbehaving code, but don’t show the code.

-kevin

Since then I have resolved the issue of this error in the RT-logs. It turns out. It was one of my templates acting up. I was using $ticketObj instead of $ticket.

I am still receiving a problem with regards to escalating the priority though.

-Aaron

As it indicates, this error is caused by something keeping a ticket
around too long.

We would need to know your actual RT version, as well as custom code
you’ve written. You may also get more information if you enable
LogStackTraces at the warning level.

It’s possible this is tied to your later question where you ask about
misbehaving code, but don’t show the code.

-kevin

This email and any files transmitted with it are confidential and may be privileged and are intended solely for the use of the individual or entity to whom they are addressed. If you are not an addressee, any unauthorised direct or indirect dissemination, distribution, publication or copying of this message and any attachments is strictly prohibited. If you have received this email in error please notify the sender immediately, and delete this email from your system. This email has been swept for viruses, but it is the responsibility of the recipient to ensure that the onward transmission, opening or use of this message and any attachments will not adversely affect its system or data.

Please carry out virus and other checks as you consider appropriate. No responsibility is accepted by SouthWestern in this regard.

SouthWestern Business Process Services Ltd.

Registered in Ireland, Company Number 377757

Registered Office: Unit B, West Cork Technology Park, Clonakilty, Co. Cork, Ireland

Directors: N. O’Leary, U. Kenny, J. Costello, P. Morrissey, K. Calnan, J. Walsh, T. Cowhig and D. O’Donohoe.