Hi Milan,I guess this is the choice of storage compacity, using a byte @flags (sqlname iFlags) and OR logic to store 3 boolean values (controlGroupMember, quarantine, seedMember) as bits in this huge volume table, versus the efficiency/performance type for searches on these 3 booleans.As you can see...

Hi Milan,So my previous post explained the constant response time behavior.Then, the query lasts for you 1,5 hour.May you give us an hint, how many nms:broadLogRcp records do you have in your instance?As comparison, for 140M of records (lines), the SQL query lasts 10 minutes with the wkf JS cnx.quer...

Yes it is weird.But with SQL Developer, Oracle underlying RDBMS could perhaps manage the query differently.Please run the query within a workflow, not through the typology / delivery in order to check.From my side the query lasts very long, because I thing the EXISTS subquery is ran over the whole d...

Hi Milan,Please may you confirm that the query executes quickly when you run it from a dedicated targeting workflow?RegardsJ-Serge

Hi Akshay,The logInfo() logError() messages of webApps and reports are written in the web.log file on the server where the webApps or reports are executed.On standalone architecture, so you can see it by using the ACC user interface Home>Monitoring>section of Process logs the web.log link.On standar...

Hi Marcin,I guess your ACC instance is On Premise hosting, because you were asking for the log path.So probably you are able to start a process with verbose mode. But the web.log file will be full of verbose details, and with the automatic logrotate you will have short time to keep production logs a...

Hi Jayesh,Yes you are totally right, it is whenever a change is done in the delivery template itself.If you need to raise new delivery on some other circumstances, you must achieve it with specific code in the workflow (as Message Center does, for example, for having different delivery execution fol...

Hi Roopal,2 solutions:use of Incremental Query activity in your workflow: each execution takes the data not already treated. So when something is suspended, it takes the old data (your weekend data) to send it at next execution planified; please see the 2nd tab of the activity, it includes the plani...

Hi Milan,Please use [url/@type] from nms:trackingLogRcp with value = optout in your Query activity.That is for the unsubscribe link in a delivery that leads either to directly set nms:recipient.@blacklist to 1, or per blacklist per channel, or nly unsubscribe for a dedicated service (and so subHisto...