Warning: "Execution has execute elements, but execution state is passed."

Comments

9 comments

  • Avatar
    Mario Ermacora

    Hi Thomas

    I haven't seen this particular warning from a Directory List node. Given it's only a warning level message, I'd expect the node to show a completed execution status and have data on the output pin - is that true in your case?

    Regards,

    Mario

    0
    Comment actions Permalink
  • Avatar
    Thomas Wong

    Hi Mario,

    Not able to get any output when I ran the node in the instance where the warning appear.

    Not sure what causes the warning... but one thing to note is that my graph contains smaller flows which are yet to be joined. I have been working on several isolated pieces, starting from different acquisition nodes and hope to join things up as I progress. 

    The node is then able to execute when I reset the entire graph, select ALL nodes and re-run.

    In fact I was trying to avoid re-run as there are huge volume of records which has been processed.

     

    Regards,

    Thomas

    0
    Comment actions Permalink
  • Avatar
    Mario Ermacora

    I'm working directly with Thomas to try to isolate and reliably reproduce this issue.

    Will then submit a support ticket if necessary.

    Mario

     

    0
    Comment actions Permalink
  • Avatar
    Jorge Arbelaez

    I found the same error when trying to execute a node which it's source is the same for different nodes. The work around that I found was to re-execute the nodes at the same time, but I don't think this is efficient. Do you guys have any solution?

     

    0
    Comment actions Permalink
  • Avatar
    Mario Ermacora

    Hi Jorge

    Does that warning appear consistently when you follow the same steps as you did the first time?

    I'm looking for a way to consistently replicate this warning, so if you can do that please email me an export LNA of your data flow with details of the steps to followed to get the warning.

    Also, please confirm you are running the latest 3.2.6 release of D3S Analyze.

    Thanks,

    Mario Ermacora

    0
    Comment actions Permalink
  • Avatar
    Jorge Arbelaez

    Hi Mario!

    yes! the concrete situation in which i'm right now is the following scenarios:

    1. When i use as an input the same source for a JDBC query Node ( to execute 2 different queries but with the same parameters), if I select both of the nodes and click in run, it runs without any issue, however if I execute first one node and then the other one I would get this warning.

    2. If i have the same source into a composite but linked in different inputs  when running the nodes that get those inputs if they are selected and run at the same time it will run without any problem, but if I run them in different time I will get the warning. 

    there are a couple of images attached to clarify both scenarios

    In regards to the version, i'm running 3.2.5

     

    Attached files

    Scenario 1.PNG
    Scenario 2.PNG

     

    0
    Comment actions Permalink
  • Avatar
    Mario Ermacora

    Hi Jorge

    A couple of further questions:

    1. Both screenshots show the two JDBC Query nodes inside a composite. Does the warning also appear when the nodes are at the top level of the data flow?

    2. Do you have any clock dependencies between an nodes in the same data-flow?

    Regards,

    Mario

    0
    Comment actions Permalink
  • Avatar
    Jorge Arbelaez

    Hi Mario

    I tried the scenario of replicating the same issue in the main data flow and i still get the same Warning (image attached).

    In regards to the clocks, I don't have clocks dependencies linked to those nodes.

     

    Attached files

    Data Flow.PNG

     

    0
    Comment actions Permalink
  • Avatar
    Mario Ermacora

    Hi Jorge

    I attempted to replicate the scenario you've described on my own D3S Analyze 3.2.6 installation, but so far haven't been able to trigger the warning.

    Tried both with JDBC Query nodes, and other nodes, at the top-level and inside a composite, and with 1 or 2 composite inputs. So there's something different and not-obvious about your data-flow that's triggering this error, or possibly the issue has already been fixed in 3.2.6.

    Can you please send me an export LNA of you data-flow so I can take a closer look (please send this directly to me via email).

    Also, when you get a chance please upgrade to the latest 3.2.7 release and let me know if you can trigger the warning in that version.

    Thanks,

    Mario

    0
    Comment actions Permalink

Please sign in to leave a comment.



Powered by Zendesk