Weird behavior with scrips

Using 3.0.10, I’ve got some strange behavior. I have a queue which has a scrip
On Correspond Notify Requestors with template Correspondence, where the template
contains {$Transaction->Content()}

Rights for the queue are assigned by group. Everyone in the department is a
member of the same group, has same watcher status, etc.

This doesnt work for one person. Anybody else in the group can click reply in
the ticket and it sends the reply to requestors. When this one person tries
though, no reply is sent and I see this in the logs:

[Mon May 17 15:17:54 2004] [info]: RT::Scrip=HASH(0xa09b4d4): Couldn’t prepare
Notify Requestors (/opt/rt3/lib/RT/Scrip_Overlay.pm:346)

If I set up a test scrip which does autoreply to requestors rather than notify
requestors, it works for everybody.

Given that the rights are assigned by group and everyone is in the same group,
and the notify requestors works for everyone else, why does it generate this
error for the one person?

Craig Schenk wrote:

Using 3.0.10, I’ve got some strange behavior. I have a queue which has a scrip
On Correspond Notify Requestors with template Correspondence, where the template
contains {$Transaction->Content()}

Rights for the queue are assigned by group. Everyone in the department is a
member of the same group, has same watcher status, etc.

This doesnt work for one person. Anybody else in the group can click reply in
the ticket and it sends the reply to requestors. When this one person tries
though, no reply is sent and I see this in the logs:

[Mon May 17 15:17:54 2004] [info]: RT::Scrip=HASH(0xa09b4d4): Couldn’t prepare
Notify Requestors (/opt/rt3/lib/RT/Scrip_Overlay.pm:346)

If I set up a test scrip which does autoreply to requestors rather than notify
requestors, it works for everybody.

Given that the rights are assigned by group and everyone is in the same group,
and the notify requestors works for everyone else, why does it generate this
error for the one person?
Look for NotifyActor in archives and RT config.

Look for NotifyActor in archives and RT config.

Dont think that’s it since the requestor is a different person from the person
who the scrip isn’t working for. I turned NotifyActor to 1, we’ll see if that
fixes things, but from reading the archives it doesn’t sound like the same
problem others reported.

Just confirmed that the problem exists regardless of the value of NotifyActor.
Anything else to check?