Mails are not properly sent
In our production region when some mails are getting triggered it's falling under broken queue entry with "pyItemStatus" as Scheduled and "pyAttempt" as 0 while leads to mails not properly sent.
When we open the case and verify it shows "Not yet sent"
| Sent: | (Not yet sent) |
No error message in the broken queue xml as it is in the scheduled status.
Any solution for this issue is much appreciated.
Hoverstate
US
Have you tried restarting agent ?
Cts
US
Yes Pravin.
Tried restarting it, but still some items are in Scheduled queue with mails are not been sent out.
PEG
GB
I'm not rightly sure how it could have ended up on the Broken queue with a pyItemStatus of Scheduled.
But can you open the full record details and see whether there is a failure reason?
Also is the pyMinimumDateTimeForProcessing set do a date in the past or the future?
Cts
US
There is no failure or error message details for this item.
<pyMinimumDateTimeForProcessing>20190422T202421.274 GMT</pyMinimumDateTimeForProcessing>
Last execution time also showing yesterday's date, but still mails are not sent.
PEG
GB
OK. Well that looks good.
Technically (and assuming your using the standard SendCorr agent) this should be running the SPPR_SYS_RESERVERQUEUEITEM_B stored procedure periodically to identify the records which are due to be processed.
So I'd anticipate that this should be picked up.
Are you able to attach the XML for that record here? (Or does it contain sensitive data)?
If the latter, are you able to redact the sensitive information first? Also could you please verify that the information in the columns matches the information in the XML, particularly the pxObjClass, pyItemStatus and pyMinimumDateTimeForProcessing.
Cts
US
Yes we are using SendCorr Agent only.
Please refer the attached Scheduled queue xml.
PEG
GB
Again, the information in the XML looks valid too.
Can you return to the SendCorr agent itself and as well as checking that it's running, verify the last run time.
(If you're looking at this through the Designer Studio, you can see this by expanding the agent, then hover the mouse over the node id, and a pop-up should appear)
Cts
US
We are yet to find the root cause of this issue. Any help on this issue is appreciated.