Hi,

Thank you for your post.

You should set the next settings for the log levels:

• Apex Code — Finest

• System — Finest

• Database — Info

• Apex Profilling — Error

• Callout — Error

• Validation — Error

• VisualForce — Error

• Workflow — Error

After this you will be able to use Apex Retrospective Debugger.

You can find more information about the work of the Apex Retrospective Debugger in the Blog post.

Regards,

Kate

Ok I changed the settings

36.0 APEX_CODE,FINEST;APEX_PROFILING,ERROR;CALLOUT,ERROR;DB,INFO;SYSTEM,FINEST;VALIDATION,ERROR;VISUALFORCE,ERROR;WORKFLOW,ERROR

But now I just get an error message that an issue was encountered and to contact support.

Hi,

Thank you for your reporting this issue.

Looks like the reason for your issue is a missed dll-file which wasn't added during the installation of Microsoft Visual Studio Shell (Isolated).

I kindly ask you to reproduce this case several times and send us your log-file.

You can do this the next way: Main Menu -> Help -> Report a Bug. Please, write several words about your issue and make sure that the check-box 'Attach Log File' is marked.

We will get the necessary information for our investigation process this way.

Thank you,

Kate

I was able to reproduce same error by doing the following:

1. Create new, empty VF page

2. Set up log levels as described in blog post

3. Open the newly created page in browser

4. Download the log in TWS

5. Try to debug with that log file

=> TWS reports error with a popup

It looks like use case is missing when log levels are set up properly but log itself doesn't have any content that is debuggable 

Hi all2human, tomic.84,

There might be different "strange" situations in the log files (for example something that's against the official SF documentation - it's a common case here).

If you can examine the log file by yourself and if there's no sensitive information in the log file - we will appreciate if you will be able to send this log file to us, so we can understand what was exactly the issue.

In case if this log file(s) does not contain any sensitive information about your project, code or data in it - you can send it directly to me (vladimir.gubanovich@welkinsuite.com).

Any way we continue working on the Retrospective Debugger and are investigating lots of different log files to cover all possible situations and to ensure that it's always working.

Thanks,

Vladimir

I don't have it anymore but I described exactly how I got this error. It shouldn't be a problem to reproduce it

Is this issue still being looked at? I am getting the same error after opening the log file. Debug log levels are all set to finest and running the latest version of welkin suite. What are some factors in the log that would cause this error?

Hi,

Thank you for your contacting us with this information.

I kindly ask you to send us a bug report directly from The Welkin Suite right after the issue is reproduced for you. You can find this functionality in the following way: Main Menu - > Help -> Report a Bug. You can enter the link to this topic as a description. Please enter your email for our feedback and enable the 'Attach Log File' checkbox. 

In addition, can you please check the log levels in your opened log file? The first string shows you the set of the debug log levels for the downloaded file.

Thank you,

Kate