Hello @assiba_johnson    This is not a bug.   internalName is unique for each record and you can have only one record for an internalName.   With this package, the Adobe campaign was trying to create a new record with the existing internalName and that is why you see this error.

The code is correct and you should see the logging in web logs

Hello @Anushka_RK    Could you please share the screenshot of the code used for the logging? If you can see other logs then it is not an access issue.

Hello @Karthik2587    You can use AEP Assurance to check the parameters and see the json payload used to send the push

Hello @Anushka_RK    Try to print the values first for all the results and see if the values exist or not. for each (var rcp in res) { %> <%= rcp.Key1 %> <%= rcp.Key2 %> <%= rcp.Language %> <%= rcp.OfferExpiryDate %> <%= rcp.Response %> <% } %>  

Hello @Anushka_RK    Here is the screenshot from my test.   Note: In the dates select the start date = yesterday's date

Hello @Anushka_RK    Try adding toString() in the values like this   ctx.vars.Key1 = rcp.Key1.toString(); ctx.vars.Key2 = rcp.Key2.toString(); ctx.vars.Language = rcp.Language.toString();   Also, If your query is returning 5 results then your ctx variables will have the value of the last iterated re...

Hello @Anushka_RK    logInfo will capture the logs in the web.log file. You can see this data in the Monitoring tab outside on the light ui.   Alternatively, you can use console.log to print anything in the console.

Hello @god_prophet    Yes, Just query the xtk:workflow schema and look for the value of keepResults column    

Hello @vani97    You will have to update the recipient email with the valid email address   If the email field is valid, then update the recipient profile with the email attrbiute   if the email field is empty, then update the recipient profile with an alternate attrbiute   Here is what you can use ...