Email account configuration for sending Notify emails
Hi,
I am trying to send notification emails on assignment shapes. I used NotifyAssignee activity on Notifications tab but I am not receiving any emails. On the email accounts page, email account connection status is OK, however I didn't configure Receiver information. In order to receive notification emails, do I need to configure Receiver information as well ?
In addition, I receive emails when I use sendsimpleemail activity.
Thanks for your support.
Accepted Solution
Pegasystems Inc.
US
The agent will only pick up Scheduled items so the broken queue items will not prevent the agent from picking up new items. As far as how to proceed, it will depend on the queue items you have waiting to get picked up and whether they still need to be processed. If you have a large number of old queue items in a Scheduled status but do not need them processed then you could remove them.
Pegasystems Inc.
US
You should just need the outbound email configured. Is the SendCorr agent running? What do you see when tracing?
EIB
PL
SendCorr agent is running with no errors. I see CorrCreate and CorrUpdate activities run with no errors on tracer, also the corr attachment is attached to work but, it says "not yet sent". Should I clean the System-Queue-DefaultEntry items on queue management ?
Pegasystems Inc.
US
In the trace, do you see the email settings applied properly when pySetNotifyParameters executes? Do you see CorrSend execute and queue the email? If you stop the SendCorr agent temporarily, do you see the queue item created? Can you then trace the agent to see what happens?
EIB
PL
I see that pySetNotifyParameters executes and properties have the correct values inside the page. I see CorrSend and Queue-For-Agent and also the item created in queue management. But in the queue management, all the attempts number counts are 0.
Pegasystems Inc.
US
Okay, so you have a queue item created for the SendCorr agent, right? Is it showing a Scheduled status and has it reached the pyMinimumDateTimeForProcessing? What do you see when tracing the SendCorr agent?
EIB
PL
Yes, item created. I see pyItemStatus as Scheduled and pyMinimumDateTimeForProcessing has value in pr_sys_queues table. When I trace the agent, I see an error on Assign-acquireWorkObject step 5 fail "Unable to open an instance using the given inputs: ASSIGN-WORKLIST ...-WORK ...-233!..." And also Data-Corr-PushNotification Send fails. The work item 233 is a very old work object. It may has errors on flow and assignments due to development process.
Its strange that when I try to trace the agent again, it says "Unable to schedule tracing for the agent Pega-ProCom:SendCorr"
I assume that the agent tries to process from the beginning of the queue, but old items have error. Thus it is not be able to process new queue items. Am I correct ? What do you think ?
Thanks.
Pegasystems Inc.
US
Yes, it should pick up the queue items based on the Scheduled status and pyMinimumDateTimeForProcessing so it would pick up the older items first. I would expect those with issues to go to the broken queue.
EIB
PL
Yes I see broken queue items. So, which action should I take to enable SendCorr agent to process newly created items? Should I remove all the queue items and try notifyAssignee activity again ?
Accepted Solution
Pegasystems Inc.
US
The agent will only pick up Scheduled items so the broken queue items will not prevent the agent from picking up new items. As far as how to proceed, it will depend on the queue items you have waiting to get picked up and whether they still need to be processed. If you have a large number of old queue items in a Scheduled status but do not need them processed then you could remove them.
EIB
PL
Thank you for all your comments. I removed all the old queue items in the agent queue, then restarted the agent. Now I receive the notify emails and also notification emails for pulse notification which is great for my requirement.