Issue in Publishing Custom resources in Adobe campaign Standard

Avatar

Avatar
Validate 1
Level 2
shyamc89450995
Level 2

Likes

4 likes

Total Posts

19 posts

Correct reply

1 solution
Top badges earned
Validate 1
Boost 3
Boost 1
Affirm 1
View profile

Avatar
Validate 1
Level 2
shyamc89450995
Level 2

Likes

4 likes

Total Posts

19 posts

Correct reply

1 solution
Top badges earned
Validate 1
Boost 3
Boost 1
Affirm 1
View profile
shyamc89450995
Level 2

14-03-2018

I have created custom resource in ACS. But, During publish i am getting below error.

Please let me know the steps to resolve the issue as i am new to the ACS.

This one is bit urgent. Can anyone guide us to resolve this cache invalidation issue?

1442231_pastedImage_0.png

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Give Back 50
Level 10
florentlb
Level 10

Likes

237 likes

Total Posts

1,109 posts

Correct reply

239 solutions
Top badges earned
Give Back 50
Give Back 5
Give Back 3
Give Back 25
Give Back 200
View profile

Avatar
Give Back 50
Level 10
florentlb
Level 10

Likes

237 likes

Total Posts

1,109 posts

Correct reply

239 solutions
Top badges earned
Give Back 50
Give Back 5
Give Back 3
Give Back 25
Give Back 200
View profile
florentlb
Level 10

04-04-2018

Hi,

Did you find an answer to your problem? Custom resources can be a bit tricky. I'd suggest to:

1. check your resources for any misconfiguration or unwanted blank field (it can happen)

2. if that does not change, try recreating your resources from scratch

3. or, contact support to have your instance investigated.

Florent

Answers (1)

Answers (1)

Avatar

Avatar
Validate 1
Level 2
shyamc89450995
Level 2

Likes

4 likes

Total Posts

19 posts

Correct reply

1 solution
Top badges earned
Validate 1
Boost 3
Boost 1
Affirm 1
View profile

Avatar
Validate 1
Level 2
shyamc89450995
Level 2

Likes

4 likes

Total Posts

19 posts

Correct reply

1 solution
Top badges earned
Validate 1
Boost 3
Boost 1
Affirm 1
View profile
shyamc89450995
Level 2

05-04-2018

Thanks Florent, We are able to resolve this issue with the help of adobe support. It was cache issue.

Regards,

Shyam