Adobe Debugger displays inaccurate calls | Community
Skip to main content
M
mrudy1
New Participant
October 23, 2023
Solved

Adobe Debugger displays inaccurate calls

  • October 23, 2023
  • 3 replies
  • 1050 views

Adobe Experience Platform Debugger shows all calls twice (including pageviews). I believe this has been happening since the new version launched on Oct 19th. We also see random alphabets for each evar/prop on the debugger (PFA image). This could be an extension issue as we see only one-call fire for page load on the browser's network tab. 

Thanks for looking into this

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Best answer by freedricktroisterlanter

    Getting the same issue with duplicate columns showing for each fire. Additionally, since this started happening, selecting "show post-processed hit" now results in an error message (text below):

     

    Something went wrong.
    We're sorry but something has gone wrong and we are unable to show this section at the moment. Try using a different section or closing and re-opening the debugger window.

    We've automatically been notified of the error but please reach out if this continues to occur.

    3 replies

    NimashaJain
    NimashaJain
    Employee
    February 6, 2024

    @rudi-shumpert @dwright-adobe Can you please look into the issue as there are 12 people who has faced same issue?

    C
    cbvcb
    New Participant
    October 25, 2023

    We also experienced the same problem starting from last week

     

      F
      freedricktroisterlanterAccepted solution
      New Participant
      October 24, 2023

      Getting the same issue with duplicate columns showing for each fire. Additionally, since this started happening, selecting "show post-processed hit" now results in an error message (text below):

       

      Something went wrong.
      We're sorry but something has gone wrong and we are unable to show this section at the moment. Try using a different section or closing and re-opening the debugger window.

      We've automatically been notified of the error but please reach out if this continues to occur.
        Terms & ConditionsAccessibility statement

        Loading footer...