The Welkin Suite Forum

Debugger incorrectly reporting wrong levels

Debugger incorrectly reporting wrong levels

  • Please log in to reply



    Posted 17 Jan 2017

    This had me scratching my head for a while.. The retrospective debugger was working great in a client org then just stopped working one day - all the different methods of getting into the debugger were failing with various errors.

    What I eventually figured out was that the difference between orgs where the debugger worked and orgs where it didn't was the first line in the log. In my case, for an org where it doesn't work, it looks like this:


    If I remove ';WAVE,INFO' from this line then save the log, I can debug it. I suspect it's having a hard time with any component it doesn't expect, not just Wave.

    1 replies to this topic



      Posted 17 Jan 2017

      Hi Dave,

      Thank you for contacting us ith this issue. 

      The reason for this is that your Organization was updated to Salesforce version Spring'17 and these are related changes. In general, yes, you're right - we were not expecting for the WAVE category in the debug logs and this why Retrospective Debugger didn't start. 

      Our developers have already fixed this issue and we will release it in TWs Spire R8 tonight.



      Kate Dulko
      Customer Relations

      The Welkin Suite

      twitter: @KateDulko
      skype id: d_katerina



      Boost Your Productivity. Get Started Today

      Try Free Trial