Hi,
I'd like to implement a regular refresh of the Recompute delivery and tracking indicators action to run on demand/more regular intervals. Is there an easy way to force this to run from a workflow?
TIA
表示
返信
いいね!の合計
Hi Alistair,
There are hourly technical workflows (Tracking and Delivery Indicators) that execute and are in charge of updating these statistics. Is there a reason why you'd want an additional workflow for this?
Hello @Craig_Thonis I think @AlistairKi is in similar situation as us. Most of the times out-of-the-box workflow fails to update the delivery and tracking indicators and then we have to manually sync the deliveries.
We created a support ticket with Adobe and the support suggested to create a custom workflow to fix the issue. Which is counter-intuitive and both processes will use the same under lying mechanism.
表示
返信
いいね!の合計
@_Manoj_Kumar_ has it correct. We are seeing instances where our deliveries are not updating as expected which requires us to manually go into each delivery affected, right click > actions > recompute delivery and tracking indicators
We are mainly seeing this on our SMS deliveries. Running the above steps clears the issue but is not ideal due to the required manual intervention
表示
返信
いいね!の合計
Hi @AlistairKi ,
Refer this blog to create JS in the workflow and automate it. (Test the script in lower environment)
Use QueryDef to fetch the deliverId and pass it on the below script as vars.deliverId,
var nmsDeliveryDirtyFlags_tracking = 1; // tracking logs (1)
var nmsDeliveryDirtyFlags_messageCounters = 8; // broad logs (1)
var flags = nmsDeliveryDirtyFlags_tracking | nmsDeliveryDirtyFlags_messageCounters; // bit operation (2)
NLWS.nmsDelivery.RecomputeStats(vars.deliveryId, flags);
Hi @AlistairKi,
Was the given solution by @ParthaSarathy helpful to resolve your query or do you still need more help here? Do let us know. In case the given solution was helpful, then kindly choose it as the 'Correct Reply'.
Thanks!
表示
返信
いいね!の合計