A/B Target Activity caching Issue while editing adding modification | Adobe Higher Education
Skip to main content
S
subha2
June 4, 2025
質問

A/B Target Activity caching Issue while editing adding modification

  • June 4, 2025
  • 2 の返信
  • 438 ビュー

Having issue while editing A/B Target Activity, When adding changes to Experience-B all the modifications is applied to Experience-A and Vice Versa in Adobe Target activity.

If both the Experience has modification it is applying the changes from Exp-B to Exp-A and Vice Versa. Having issues when trying to Fix VAR where I have to delete all modifications from both the experience and Adding back again to fix VAR.

How to resolve the caching issue happening when editing A/B test activity?

このトピックへの返信は締め切られました。

2 の返信

NarenKotipalli
NarenKotipalli
Level 3
June 5, 2025

@subha2I faced a similar issue, but I observed that the problem isn't due to caching—it's actually a loading error. When switching from Exp B to Exp A, the Modifications panel should reload to show the respective modifications, but instead, it continues to display Exp B’s modifications. You can report this as a bug to the Adobe support team; as a workaround, try saving and reloading the activity or switch between experiences until the correct modifications appear.

    pradnya_balvir
    Community Advisor
    pradnya_balvirCommunity Advisor
    Community Advisor
    June 5, 2025

    Hi @subha2 ,

     

    This is a common and frustrating issue in Adobe Target’s Visual Experience Composer (VEC) — where modifications made in one experience (e.g., Experience B) mysteriously apply to Experience A and vice versa. It’s usually tied to DOM caching issues, improper selector handling, or session persistence bugs in the browser or Target itself.

     

    Clear Browser Cache & Disable Extensions

    Before editing:

    • Clear cache (esp. local storage/sessionStorage).
    • Use incognito mode or a clean browser profile.
    • Disable interfering browser extensions like ad blockers, tag debuggers, or React dev tools — these can conflict with VEC rendering.

    Always Reload VEC After Editing One Experience

    • Edit Experience A → Save → Reload VEC → Edit Experience B
    • This avoids session merge issues across experiences.

    Still exist then 

    You can report a persistent bug to Adobe Support by including:

    • Activity ID
    • URL of test page
    • Steps to reproduce the experience modification conflict
    • Screenshots or screen recordings
      契約条件Accessibility statement

      Loading footer...