Failure Reasons and Import Workflow | Community
Skip to main content
R
rohanpat-1
Level 2
June 10, 2020
Solved

Failure Reasons and Import Workflow

  • June 10, 2020
  • 2 replies
  • 5240 views

Hi,

Basically, I had two questions, since I am integrating my MTA server with adobe, upon delivery I need to trace back the stats back to adobe for reporting.

 

1. With resp to failure reasons, like mail box full, not connected, refused, unreachable, what table should I refer to insert the values? Would it be directly 'nmsdeliverylogstats'? Any other tables I need to take care?
Because the delivery success / failures I am inserting in 'nmsbroadlogrcp' table and they auto populate in 'nmsdeliverylogstats'.

 

2. Is it possible to import / create work-flow in a way to insert the entries in above 2-3 tables at the same time? Currently, my work-flow just inserts entries into 'nmsbroadlogrcp'. Any reference for example?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by isahore

Hi @rohanpat-1 ,

You need to update the failure reasons in the nms:broadLogMsg schema, linked to the nms:broadLogRcp schema with msg-id field. Below screenshot should help.

 For your second question, the answer is yes. How exactly are you receiving the response from the custom MTA? API, files, or something else. Based on that you can build a mechanism to update all tables with proper linked items.

Cheers.

2 replies

isahore
Community Advisor
isahoreCommunity AdvisorAccepted solution
Community Advisor
June 10, 2020

Hi @rohanpat-1 ,

You need to update the failure reasons in the nms:broadLogMsg schema, linked to the nms:broadLogRcp schema with msg-id field. Below screenshot should help.

 For your second question, the answer is yes. How exactly are you receiving the response from the custom MTA? API, files, or something else. Based on that you can build a mechanism to update all tables with proper linked items.

Cheers.

    R
    rohanpat-1Author
    Level 2
    June 15, 2020
    Thanks @2108451 for the explanation. I did follow your steps but no luck. Instead of going via import work-flow route, I manually inserted new entry in nmsbroadlogmsg table with mailbox full error against soft bounce event code, based on msgId, inserted similar kind of record in nmsbroadlogrcp with other details like success / failure and deliveryID. Now my expectation was in the background Adobe's job would insert the related entries in nmsdeliverylogstats but that wasn't the case, as a result UI didn't had the related reporting. Could you please suggest where am I going wrong and my understanding with the flow is correct? I did vice versa as well... like inserting first in nmsbroadlogrcp followed by nmsbroadlogmsg, but didn't succeed.
    Venu_Reddy
    Venu_Reddy
    Level 6
    June 11, 2020

    Hi @rohanpat-1 ,

     

    For the first question, the failure reasons will save automatically into Non Deliverable management (Location as Adminstration -- Campaign Management -- non deliverables and addresses).

     

    You can find all the results here and hope it helps you.

    Terms & ConditionsAccessibility statement

    Loading footer...