Hi @daniellee605809,    You can't directly share the web@default log journal, but you can manage those errors in a good way. I would try building a workflow that queries the log table (xtk:logMsg) for entries containing (nms:webApp Error) and stores them in a custom table. Then, you can create a sim...

Hi @A_B_SE,    I think you can try adding a clickable link in the Preview tab by extending the nms:delivery input form. I share with you a possible code that could work, it builds the preview URL using the current deliveryId and a selected test recipient, then it opens it in the browser: <button lab...

Hi @Michael_Soprano,    If you would like to send audiences to campaign v8, you can use Adobe Campaign Managed Cloud Servies for streaming (real-time) activation and Adobe Campaign connection for batch (file-based) transfers. The Managed Cloud Services connector is for cloud - hosted v8 environments...

Hi @bsm11, Yes, that's correct Broja. As @LakshmiPravallika mentioned, the xtk:workflowLog schema is the right place to check, you can use the message and logDate field to identify when the workflow started and ended, since there's no direct attribute for those timestamps.   Best,  Celia

Hi @HectorAb,    You might be getting a 404 because you're calling the wrong endpoint or resource name.   In Adobe Campaign Standard, you can retrieve the full definition of standard and custom resources through metadata endpoints.    For standard resources: GET https://mc.adobe.io/<tenant>/campaign...

Hi @GirishwarsinghCh,    For large csv files you can use BeyondCompare or Diffinity and if this is a process that is going to be repeated again you should think about implementing an script.   Best,  Celia

Hi @o_X,    I think it is not possible to use session write collection on workflow temp tables, since those aren't linked to any data schema. These tables are temporary tables created only during execution so the write APIs don't apply.    The best approach is to avoid row by row updates and use a s...

Hi @A_B_SE,    Unfortunately, Adobe Campaign Classic doesn't support generating a single preview link that displays all conditional logic without a recipient context, since personalization will require always data to resolve. In the Preview tab, you can review the delivery using a recipient, a seed ...

Hi @neeliv7,    Thanks for coming back, instead of pause, try with stop this should allow the prepare step to correctly reschedule the delivery.    Don't hesitate to come back if it does not work.  Best,  Celia

Hi @neeliv7,    Updating scheduling.contactDate alone won't reschedule a "Start pending" delivery sibce the scheduler catches it at prepare time. You need to pause the delivery update the contact date and then re-run PrepareFromId() to rebuild scheduling data. After that, resume it with Play().   Tr...