Message Center Tables | Community
Skip to main content
robertc66522596
robertc66522596
Level 4
August 31, 2024
Solved

Message Center Tables

  • August 31, 2024
  • 2 replies
  • 1105 views

Hello,

 

Can someone please confirm what these fields represent with respect to Message Center?

 

  •  nms:eventHisto > Process requested on (@scheduled)
  • nms:eventHisto > Process started on (@processing)
  •  nms:eventHisto > Processed on (@processed)

 

My understanding is that it is when inbound events are requested, started, and then processed from the Adobe system itself. Once it is processed, it is ready to be sent outbound and the time stamps have nothing to do with the delivery itself. Am I incorrect in that assessment?

 

Thank you for your help!

Robbie

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 robertc66522596

Hi Again,

 

After meeting with support, i was informed that @processed actually is dependent on the delivery itself. That field updates based on receiving information back (essentially the same as delivery logs). Interesting and confusing, but good to note.

2 replies

MeitMedia
MeitMedia
Level 4
September 1, 2024

Hi @robertc66522596 ,

 

Your understanding is mostly correct, but let me clarify each field in the context of ACC's Message Center:

nms:eventHisto > Process requested on (@scheduled):
This field represents the timestamp when the inbound event was requested for processing by the system. Essentially, it's the moment when the system schedules the event for further processing.

nms:eventHisto > Process started on (@processing):
This field indicates the timestamp when the actual processing of the event begins. This is when the system starts handling the event data, which includes things like personalization, template application, and potentially other business logic defined in the event's processing workflow.

nms:eventHisto > Processed on (@processed):
This field shows the timestamp when the processing of the event is completed. At this point, the event is fully processed and is ready to be sent out, typically as an outbound message, such as an email or SMS.

 

These timestamps indeed track the lifecycle of inbound events within the Message Center, from being scheduled to being fully processed.
They are not directly related to the actual delivery timestamp. Once the event is processed (@processed), the message is then ready to be sent, but the delivery itself (when the message is actually sent to the recipient) would have its own timestamp in the delivery logs.

 

Best regards,

MEIT MEDIA (https://www.meitmedia.com)

Find us on LinkedIn

Contact Us: infomeitmedia@gmail.com

 

 

    robertc66522596
    robertc66522596Author
    Level 4
    September 3, 2024

    Hi @meitmedia -- thank you!

     

    This is exactly what I was looking for, thank you for the confirmation and additional information.

     

    I have raised this issue to our account and support teams after our Message Center go live and they've been ignoring these timestamps, insisting the delay is on the receiving side...

     

    This gives me the confidence to continue pushing back. Thanks!

      robertc66522596
      robertc66522596AuthorAccepted solution
      Level 4
      September 5, 2024

      Hi Again,

       

      After meeting with support, i was informed that @processed actually is dependent on the delivery itself. That field updates based on receiving information back (essentially the same as delivery logs). Interesting and confusing, but good to note.

        Terms & ConditionsAccessibility statement

        Loading footer...