Leiste mit Community-Erfolgen erweitern.

Submissions are now open for the 2026 Adobe Experience Maker Awards

Mark Solution

Diese Konversation wurde aufgrund von Inaktivität geschlossen. Bitte erstellen Sie einen neuen Post.

GELÖST

Error during Publication (Custom Resources)

Avatar

Employee Advisor

Hello,

I created a custom resource and did the publication. It all worked fine (there was a warning in the logs at this time too). I then redrafted it and it got successfully deleted too with same warning in the logs as below:

shelly-goel_0-1607575413883.png

I have not experienced any issue but this warning is now appearing every time during publishing so I wanted to understand what it is, it's impact and how to fix it?

Thanks

1 Akzeptierte Lösung

Avatar

Korrekte Antwort von
Employee Advisor

I was able to resolve this error. I went through previous publication logs to see when did this error started coming. I checked all the changes that happened in that particular publication where this error first appeared and noticed extensions in oob resource. I redrafted that resource and did another publication and the error was removed.

 

Lösung in ursprünglichem Beitrag anzeigen

4 Antworten

Avatar

Level 9

I Don't think there is any impact, also neolane is an old system and no longer used correct? May be that instance has some references to it which is triggering that warning message.

Avatar

Korrekte Antwort von
Employee Advisor

I was able to resolve this error. I went through previous publication logs to see when did this error started coming. I checked all the changes that happened in that particular publication where this error first appeared and noticed extensions in oob resource. I redrafted that resource and did another publication and the error was removed.

 

Avatar

Level 9
@shelly-goel , just curious why the intial error was pointing to neolane?

Avatar

Employee Advisor

@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.