Success without seed indicators stuck | Community
Skip to main content
Marcel_Szimonisz
Community Advisor
Community Advisor
July 3, 2023
Solved

Success without seed indicators stuck

  • July 3, 2023
  • 1 reply
  • 2726 views

Hello,
can someone shed some light into the issue we experience, why some indicators stuck and stay on 0 all the time.  In the example this indicator should be 18


We are using mid-sourcing I guess the adobe support has to take a look into it?

There is technical workflow pulling these indicators but that works without any problem.

EDIT: I have found mitigation of this issue https://experienceleaguecommunities.adobe.com/t5/adobe-campaign-classic-questions/how-and-where-calculated-indicators-for-deliveries/td-p/572052
Marcel

 

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 aggabhi

Hi @marcel_szimonisz ,

 

Can you check if you are getting data in  nms:trackingLogRcp table for tracking logs of your respective delivery.

 

In case you are getting data there, it means OOTB workflow is picking the data correctly from mid sourcing but somehow in reports it is not getting reflected.

 

I have seen the same issue in some of the old builds. 

 

Kindly check and let me know, accordingly we can check more on same.

 

Regards

Abhishek

1 reply

aggabhiAccepted solution
Level 5
July 3, 2023

Hi @marcel_szimonisz ,

 

Can you check if you are getting data in  nms:trackingLogRcp table for tracking logs of your respective delivery.

 

In case you are getting data there, it means OOTB workflow is picking the data correctly from mid sourcing but somehow in reports it is not getting reflected.

 

I have seen the same issue in some of the old builds. 

 

Kindly check and let me know, accordingly we can check more on same.

 

Regards

Abhishek

Marcel_Szimonisz
Community Advisor
Community Advisor
July 3, 2023

Hello @aggabhi ,

I did action on delivery and run "Recompute delivery and tracking indicators" and the success without seeds populated. Even though it is temporary i do not understand why its not recaulculated in next run of proces taking care of this.


marcel

Marcel_Szimonisz
Community Advisor
Community Advisor
July 4, 2023

Hi @marcel_szimonisz ,

 

I would recommend you to just check the tracking workflow in technical workflow section and check if same is working correctly or not.

 

Ideally it should be running in every 1 hour for updating of tracking logs.

 

 

 

If your tracking workflow is also working, I would recommend checking with Adobe support why it is not getting updated on your out of box reports.

 

There are sone JSSP files which are present as OOTB and used to update the delivery reports.

 

REgards

Abhishek


Hello @aggabhi,

all workflows are running. There is no error in the console:

  • Tracking
  • Mid-sourcing (delivery counters)
  • Mid-sourcing (delivery logs)

We will try to open ticket with adobe support directly

 

Marcel