Aggressive page caching in VEC

[yuhuisg]

Does Target VEC employ some kind of aggressive page caching, particularly when setting up experiences?

Creating a new experience

Steps to reproduce:

1. Set up an Experience Targeting (XT) activity.
2. Modify Experience A.
3. Add a new Experience B, with no modifications applied.

Expected result: Experience B shows the contents of the original page.

Actual result: Experience B shows the same contents+modifications as Experience A.

Removing modifications

Steps to reproduce:

1. Set up an Experience Targeting (XT) activity.
2. Modify Experience A.
3. Remove the modifications from Experience A.

Expected result: Experience A shows the contents of the original page.

Actual result: Experience A still shows the contents+modifications.

[Bhuwan_B]

@yuhuisg Please check Limitations Section of VEC Best Practices document, if that helps :

https://experienceleague.adobe.com/docs/target/using/experiences/vec/experience-composer-best-practi...

[yuhuisg · Accepted solution]

Unfortunately, none of the caveats/limitations listed there apply in this case. According to what I've stated, this looks more like a bug in VEC itself.