@sufiyanp5432 Please check if you've the latest version of maven and maven-scr-plugin as well as it's dependencies.Does this exception come only for -PautoInstallBundle or with -PautoInstallPackage as well and any recent changes to the project setup? Please check if maven-scr-plugin is setup as per ...

@sravs508 Try running npm update and also check config.yaml is well formed.If this doesn't help, you could try re-installing node and npm.

Hi @YS-ST With the limited information on what you've done so far, it looks like the provisioning and configuration is not done from Adobe end. If not already done, you would have to send a request to Adobe for this as detailed below:https://experienceleague.adobe.com/docs/campaign-standard/using/in...

@mmbb110Okay got the issue. Considering there is not much flexibililty with notifications schedule, I could suggest you to go for a workaround where the deliveries are scheduled for 10-15 minutes prior to existing timings (9:50, 10:50 and so on) as you have the option of choosing precise time in del...

@mmbb110 Yes it's a global setting and cannot be applied individually. What's the random pattern do you see when you set it to 55 or 60 mins? It would be sent after every 60 mins right?

@michelle_lowThe entire string may or may not match as is because of the quote inside the quote, class applied could be different or character escaping. I had earlier tried below code and it was working. Match operation would be much more flexible and would also cater to scenario if 'DefaultSenderNa...

@mmbb110As per my understanding, ACS is the containerized/ cloud native form of campaign classic (neolane originally) and internally it's possible that container locations/ paths can have 'neolane' references.

@mmbb110 Default frequency is 10 minutes, did you try setting 60 for 'NmsDlvAlerting_frequency' options?

@aman_goyal_15Yes that's the case when you're extending core component model. For your custom component model, you can directly pass the resource and it will work (unless resource is null).The constraint in this approach would be that it would not return the values post model transformation but the ...

@Gokul_Agiwal Okay, let confirm my understanding. [1] You're getting the issue when consent is provided using Adobe.optIn.approveAll() but works fine with Adone.optIn.approve(categories, true)? (this is contradictory to your original post) [2] When do you see the console error - on initial page load...