hello @dhfw I have observed the same symptoms in the instances I have previously worked on. My analysis aligns with yours, as I had concluded that these ghost workflows are created during the execution of the tracking log retrieval workflow (internally name of the workflow: "tracking"). In this trac...

hello @wankang,try :var body = request.getBodyAsString(); var jsonBody = JSON.parse(body); Br,Amine

sorry for the delayed answer. Normaly OOTB in marketing instance this table is not populated. I'm guessing that there is a technical custom workflow that feeds it by collecting information from MidSourcing instance. if it's the case check if the workflow is started and running fine.you can look for ...

@A_B_SE  Can you take a dozen delivery-ids from the nms:deliveryStat schema and check if they correspond to real delivery ids in the nms:delivery schema. Br,Amine

Hello @A_B_SE  Are you in a MidSourcing configuration ?  Br,Amine

Super helpful @david--garcia , thank you.Where can we find more documents like this ?Thanks,Amine 

Hello @dhfwTry without the (*) : <proxyConfig enabled="1" override="localhost*,*test.com*,*sample.com*,10.119.20.14" useSingleProxy="0">It works for me like this.Br,Amine

Hello @abhinav99,   Did you do a build upgrade recently ?    Br, Amine

Hello @TJFORCE68 ,   Try this :  DELETE FROM abcMySchema WHERE sWorkflowName = '<%= instance.label %>';   Br, Amine

hello @NeelamB91,   If you want an even simpler solution, you can put directly the bellow code in the script tab of the delivery activity : delivery.operation_id=instance.operation_id; delivery.workflow_id=instance.id; Like this :  With this solution, you'll have one less JS activity in your workfl...