Data Error log

Comments

2 comments

  • Avatar
    Nik

    The first thing is to match timestamps to what you/users are doing at that time.

    This looks familiar too so I will look in our logs tomorrow. 

    0
    Comment actions Permalink
  • Avatar
    Nik

    I found two instances of the error from yesterday. By timestamp I matched both to the log/info file to assigning an eform activity. Here is one example:

    From log/error:

    2019-01-16 14:44:43.253 >>> WFDataAccessLogic.ParseDateTime, DateTime FormatException, s=66, exception=String was not recognized as a valid DateTime.

    From log/info:

    2019-01-16 14:44:43.269 >>> eFormAW_AssignWorkItem, Activity Instance=Prototype

    In our process model we have a date calculation activity immediately preceding the 'Prototype' task activity:

    However I looked at all of the configuration of the DateDiff shape and found nothing wrong. So I looked at the Prototype activity itself. We are using an integer process data variable from the DateDiff shape to assign the Time To Complete in the Prototype shape. The manage center shows that it took the value of the process data variable. In our case it is 66 days (s=66), which was correct. 

    The documentation for that field says that process data variables are not allowed. So, the issue is either in the DateDiff shape, if the developer has a datetime format wrong, or in the Prototype shape just the fact that we are using a process data variable where we are not supposed to be. Perhaps even though the variable is an integer, it gets converted to a string and then tries to do a parse from there(which if true, seems to work but throws an error first)

    Either way I found nothing wrong with the data in the processes which invoked the error yesterday. Can you look into yours, see what you find, and report back? I'm curious.

    Thanks and good luck,

    Nik

    0
    Comment actions Permalink

Please sign in to leave a comment.