The Welkin Suite Forum

NotParsedLogEventTypeException: Can not parse 'CODE_UNIT_STARTED' with 6 arguments



NotParsedLogEventTypeException: Can not parse 'CODE_UNIT_STARTED' with 6 arguments

  • Please log in to reply

#1
windows version welkinsuite

dave

    Posted 07 May 2018 and edited 08 May 2018

    I started getting this error today when opening some debug logs. 


    The actual exception seems to be this:

    WelkinSuite.Common.Extensions.NotParsedLogEventTypeException: Can not parse 'CODE_UNIT_STARTED' with 6 arguments. 
    	Log event parameters: '01qW00000004oII|CaseTrigger on Case trigger event BeforeUpdate|__sfdc_trigger/CaseTrigger'
    	Original message: 'Value does not fall within the expected range.'
    	at WelkinSuite.ApexLogParser.Implementation.LogEntryFactory.CreateLogEntry(String rawText, Int32 logLineNumber)
    	at WelkinSuite.ApexLogParser.Implementation.ApexLogParser.ParseLogEntry(String logEntryText, Int32 logLineNumber)
    	at WelkinSuite.EditorExtensions.ApexLogs.Classifier.ApexLogsClassifier.GetClassificationSpans(SnapshotSpan span)
    	at Microsoft.VisualStudio.Text.Classification.Implementation.ClassifierTagger.<GetTags>d__0.MoveNext()
    	at Microsoft.VisualStudio.Text.Tagging.Implementation.TagAggregator`1.<GetTagsForBuffer>d__5.MoveNext()

    I'm guessing it is having a hard time with this line:

    09:13:30.713 (13082143341)|CODE_UNIT_STARTED|[EXTERNAL]|01qW00000004oII|CaseTrigger on Case trigger event BeforeUpdate|__sfdc_trigger/CaseTrigger

    39.0 APEX_CODE,FINEST;APEX_PROFILING,INFO;CALLOUT,INFO;DB,INFO;NBA,INFO;SYSTEM,FINE;VALIDATION,INFO;VISUALFORCE,FINE;WAVE,INFO;WORKFLOW,INFO
    

     This is making it difficult to do debugging. Is there anything I can do to prevent this exception? Maybe some edit I can make to the log file?



    2 replies to this topic

    #2

    kate.dulko

      Posted 08 May 2018

      Hi Dave,


      Thank you for sharing this with us.


      A reason for the issue is updated structure of log files on sandboxes which were moved to Summer'18 Salesforce version. According to changes in this SF version, some of the entries have another structure or another set of parameters.

      This is why the IDE cannot parse some entries properly.


      Our developers are working on this and we are going to include the necessary changes to the nearest version of TWS.

      This version will be available for you the nearest days.


      Best Regards,

      Kate


      Kate Dulko
      Customer Relations

      The Welkin Suite

      twitter: @KateDulko
      skype id: d_katerina
      e-mail: kate.dulko@welkinsuite.com

       

        


      #3

      dave

        Posted 08 May 2018

        Cool. Thanks, Kate.






        Boost Your Productivity. Get Started Today

        Try Free Trial