Launch Configuration ignoring staging library

Avatar

Avatar
Boost 1
Level 1
JohnPurchase
Level 1

Like

1 like

Total Posts

7 posts

Correct reply

0 solutions
Top badges earned
Boost 1
View profile

Avatar
Boost 1
Level 1
JohnPurchase
Level 1

Like

1 like

Total Posts

7 posts

Correct reply

0 solutions
Top badges earned
Boost 1
View profile
JohnPurchase
Level 1

27-03-2020

I am setting up an AEM / Analytics integration and have run into the problem that my staging configuration is being ignored on the staging server - the production configuration is always used. I've gotten around this on the staging server by using putting the incorrect (staging) URL in the production configuration. This prevents staging requests from polluting the data, but isn't ideal. I still have the problem that the production author is not using the staging library.

How does a server determine which of the configurations it should use? I would have guessed run mode, but these are set as expected - using "author", "publish", "stage", and "prod" where applicable.

Accepted Solutions (0)

Answers (1)

Answers (1)

Avatar

Avatar
Give Back 5
Employee
vanegi
Employee

Likes

392 likes

Total Posts

378 posts

Correct reply

148 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back 10
Give Back
Boost 50
View profile

Avatar
Give Back 5
Employee
vanegi
Employee

Likes

392 likes

Total Posts

378 posts

Correct reply

148 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back 10
Give Back
Boost 50
View profile
vanegi
Employee

16-07-2020

Ideally it should pick as per the runmodes. Can you check if there is any custom config present under /apps/my-project/config.local which may be overriding here?