@KD1 , 1. In Case 2, where the Target Dimension is Recipient and the Filtering Dimension is Delivery Logs, is this the best approach for querying the database? - Yes, This is the best approach. You can refer this document explaining why this is best. 2. What should be the Target Dimension and Filter...

@KD1 , It depends on the field you select in 'Add data'. In keeping Targeting dimension as recipient and filtering dimension as BroadLogRcp, there are 2 scenarios. In scenario-A, if you select only 'address' and [recipient/@id] and any other fields of the recipient which has same value in the Query ...

@KD1 , is the targeting dimension is broadLogRcp?

@KD1 , Share the configurations of Query-2. This might be if you had configured group-by in query's Add data with recipient I'd and any other fields from broadLog, say for example recipient I'd with broadLogRcp I'd or with event date or with delivery I'd etc

Hi @KD1 , In both the configurations the output will be one record (as the Targeting dimension is recipient). Whereas if the targeting dimension is broadLogRcp, then the output will be 2 records as per your scenario  Filtering dimensions 

Hi @SankaravelNa , In app subscription schema you can find all the log details like registration date, token, device name and every details related to it.

Hi @ayushhtiwari , You can run the script provided by Amit in the below thread Stop the paused workflows (Test the script in lower environment)

Hi @god_prophet , You can create dbindex for your attribute and mention unique="true" Example, <dbindex name="myIndex" unique="true">       <keyfield xpath="@myField"/>   </dbindex>  

@MariBa , DateOnly(@depatureDateField) equals to DateOnly(AddDays(GetDate(),2 ))

@MariBa ,If your field DPT_DTTM is of date / datetime data type, then it should be like WeekDay(@DPT_DTTM) equal to 6