The Welkin Suite Forum

Debug log filtering & Deployment Issue

Debug log filtering & Deployment Issue

  • Please log in to reply

windows version welkinsuite


    Posted 09 May 2018 and edited 15 May 2018

    Hi there! I am evaluating Welkin Suite for purchase (using the trial) and am running into a couple issue with basic things. It is probably just operator error, so please set me straight:

    1) Debug log filtering. I open debug log and top section is empty. I click "Show Only User Debug Messages" and still empty, and the bottom does not appear to be filtered. How do I make this work?

    2) Deployment - I wanted to deply a trigger and a couple related classes to production. I went through the process, and after I chose to select my own tests, it displays a screen with a lot of tests, however the ones I need are not in it at all, whether I scroll or filter. In fact, many tests seem to be missing. I ended up just using a changeset which I would like to avoid. Thoughts?



    1 replies to this topic



      Posted 15 May 2018

      Hi Gabriel,

      Thank you for your post and for sharing the issues which you are faced with.

      Regarding the debug log filtering, may I please clarify with you if you work on log files from a sandbox and if this sandbox was already moved to the Summer'18 Salesforce version? 

      A reason for my questions is that there are some changes related to debug log files on updated environments, for example, another structure of some log entries or another set of parameters. This is why the IDE cannot parse a log file properly, and you get the empty tree-view of your log file.

      We handled this in the latest version of TWS (Bloom R18), so I kindly ask you to let me know if the same issue is reproduced after updating the IDE.

      If you have another case, or if the issue is reproduced on the Bloom R18 TWS version, please send us a bug report with the attached log files directly from the IDE - you can find this functionality in the menu Help -> Report a Bug, please put your email and enable the 'Attach Log File' checkbox. This way we would receive your TWS log files which could provide us with an additional information about a reason for this issue.

      As for the missed tests when you are going to deploy, can you please tell me if you have more then 2 thousand tests on your production organization?

      We are aware of the issue that the IDE retrieves not all tests in this case, and we will fix this in the next version of TWS.

      If this case doesn't apply to your org, I kindly ask you to follow the next steps:

           1. please execute the following query in the Developer Console on your organization (please also check the “Use Tooling API” there):
               select Id, Name, NamespacePrefix, SymbolTable from ApexClass;

           2. check if you can see the SymbolTable data for classes that are missed in the list during the deployment;

           3. if there’s no information for them – you can try executing the “Compile All Classes” action in the org (Setup -> Apex Classes), so Salesforce will refresh the data.

      After this, please check if the necessary tests will be available for you during the deployment process.

      Looking forward to your response, and we will be happy to help you.

      Thank you,


      Kate Dulko
      Customer Relations

      The Welkin Suite

      twitter: @KateDulko
      skype id: d_katerina



      Boost Your Productivity. Get Started Today

      Try Free Trial