The Stop and Start are associated with different filters. Sometimes it
can be a challenge to decide which ones match up. It's kind of hard to
tell from the snippets but I do think the notify filter is being
triggered but is then being passed over.  I would expect to see similar
lines like those that follow the Notify line that note the reassignment
of the ticket.

You should open the Groups form and search for the Group, then push the
Show Members button.  Seems like there is something up with that Group.
You may even want to add yourself for another test.

Dave

-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Hromyak, Nicholas (DHCS-ITSD)
Sent: Tuesday, July 03, 2007 11:34 AM
To: [email protected]
Subject: Re: Email limitation ARS 6.3

IS this the filter set for a NULL group that you are referring?

 

This is in beginning of Phase 3.  I didn't realize Phase 3 stops and
restarts multiple times.

 

<FLTR> <TID: 0000005648> <RPC ID: 0015210595> <Queue: Fast      >
<Client-RPC: 390620   > <USER: nhromyaka                     > /* Mon
Jul 02 2007 11:48:13.6330 */Start filter processing -- Operation -
CREATE

<FLTR> <TID: 0000005648> <RPC ID: 0015210595> <Queue: Fast      >
<Client-RPC: 390620   > <USER: nhromyaka                     >      AR
System Email Messages - <NULL>

<FLTR> <TID: 0000005648> <RPC ID: 0015210595> <Queue: Fast      >
<Client-RPC: 390620   > <USER: nhromyaka                     > Checking
AR System Email Messages Check Default Mailbox (300)

<FLTR> <TID: 0000005648> <RPC ID: 0015210595> <Queue: Fast      >
<Client-RPC: 390620   > <USER: nhromyaka                     >    -->
Failed qualification

 

 

 

Further down the log 

 

 

 

 

 

<FLTR> <TID: 0000005648> <RPC ID: 0015210595> <Queue: Fast      >
<Client-RPC: 390620   > <USER: nhromyaka                     > /* Mon
Jul 02 2007 11:48:13.6800 */     Restart of filter processing (phase 3)

<FLTR> <TID: 0000005648> <RPC ID: 0015210595> <Queue: Fast      >
<Client-RPC: 390620   > <USER: nhromyaka                     > /* Mon
Jul 02 2007 11:48:13.6800 */Stop filter processing

<FLTR> <TID: 0000005648> <RPC ID: 0015210595> <Queue: Fast      >
<Client-RPC: 390620   > <USER: nhromyaka                     >
0: Notify

<FLTR> <TID: 0000005648> <RPC ID: 0015210595> <Queue: Fast      >
<Client-RPC: 390620   > <USER: nhromyaka                     >
Priority: 0   Mechanism: Default   To: CDPH-CHCQ-LFS-Help

<FLTR> <TID: 0000005648> <RPC ID: 0015210595> <Queue: Fast      >
<Client-RPC: 390620   > <USER: nhromyaka                     >
Change CHG000000008373, Low request urgency, has been reassigned to
group GROUP-Remedy.

<FLTR> <TID: 0000005648> <RPC ID: 0015210595> <Queue: Fast      >
<Client-RPC: 390620   > <USER: nhromyaka                     >
Change CHG000000008373 (server
DEPARTMENTEISRMD01.intra.Department.ca.gov) has been reassigned to group
GROUP-Remedy.  No longer work on this entry, but contact GROUP-Remedy
with any additional information.  

Short Desc: TEST-Remedy Application - Request notification

Request Urgency: Low

 

 

 

<FLTR> <TID: 0000005648> <RPC ID: 0015210595> <Queue: Fast      >
<Client-RPC: 390620   > <USER: nhromyaka                     > /* Mon
Jul 02 2007 11:48:13.6950 */Stop filter processing

<FLTR> <TID: 0000005648> <RPC ID: 0015210595> <Queue: Fast      >
<Client-RPC: 390620   > <USER: nhromyaka                     > /* Mon
Jul 02 2007 11:48:13.6950 */     Restart of filter processing (phase 3)

<FLTR> <TID: 0000005648> <RPC ID: 0015210595> <Queue: Fast      >
<Client-RPC: 390620   > <USER: nhromyaka                     > /* Mon
Jul 02 2007 11:48:13.6950 */Stop filter processing

<FLTR> <TID: 0000005648> <RPC ID: 0015210595> <Queue: Fast      >
<Client-RPC: 390620   > <USER: nhromyaka                     > /* Mon
Jul 02 2007 11:48:13.6950 */     Restart of filter processing (phase 3)

<FLTR> <TID: 0000005648> <RPC ID: 0015210595> <Queue: Fast      >
<Client-RPC: 390620   > <USER: nhromyaka                     > /* Mon
Jul 02 2007 11:48:13.6950 */Stop filter processing

<FLTR> <TID: 0000003372> <RPC ID: 0015210602> <Queue: Fast      >
<Client-RPC: 390620   > <USER: nhromyaka                     > /* Mon
Jul 02 2007 11:48:16.1010 */Start filter processing -- Operation - GET

<FLTR> <TID: 0000003372> <RPC ID: 0015210602> <Queue: Fast      >
<Client-RPC: 390620   > <USER: nhromyaka                     >
CHG:Change - CHG000000008373

<FLTR> <TID: 0000003372> <RPC ID: 0015210602> <Queue: Fast      >
<Client-RPC: 390620   > <USER: nhromyaka                     > /* Mon
Jul 02 2007 11:48:16.1010 */     End of filter processing (phase 1)

<FLTR> <TID: 0000003372> <RPC ID: 0015210602> <Queue: Fast      >
<Client-RPC: 390620   > <USER: nhromyaka                     > /* Mon
Jul 02 2007 11:48:16.1010 */     Restart of filter processing (phase 3)

<FLTR> <TID: 0000003372> <RPC ID: 0015210602> <Queue: Fast      >
<Client-RPC: 390620   > <USER: nhromyaka                     > /* Mon
Jul 02 2007 11:48:16.1010 */Stop filter processing

<WFLG> /* Mon Jul 02 2007 11:48:23 */

<WFLG> Workflow Trace Log -- OFF

________________________________

From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Shellman, David
Sent: Monday, July 02, 2007 4:52 PM
To: [email protected]
Subject: Re: Email limitation ARS 6.3

 

Our processes are all home grown and we use the AR Groups solely as
permission Groups.  We have our own Support Group routines.

Take a hard look at the filter logs.  We have also found that if the To
field is blank, even if the CC field is not, the filter logs will show
it firing and the notify process will be defered to phase 3.  Then in
phase 3 the notify fails.

So place close attention to the filter logs, especially the phase 3
push.  It may be that for some reason the group is resolving to a null
group.

Dave
--------------------------
[EMAIL PROTECTED] (Wireless)

----- Original Message -----
From: Action Request System discussion list(ARSList)

________________________________________________________________________
_______
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where
the Answers Are"

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the 
Answers Are"

Reply via email to