Customer Portal

Query on RunGraph component

Comments 2

  • Avatar
    Vladi
    0
    Comment actions Permalink
    Hi Balaji,
    generally speaking, we recommend using the ExecuteGraph component over the RunGraph component as a general rule. You can think of ExecuteGraph as a successor to RunGraph. In other words, RunGraph is rather obsolete and minimal maintenance and development attention has been paid to this component recently. In other words, RunGraph is an obsolete component that hasn't been maintained for quite some time now so it is prone to cause unforeseen issues in general, e.g. malfunctioning passing of parameters. The reason is that we have developed a similar but more enhanced and powerful component called ExecuteGraph which is considered as RunGraph's superseder (and RunGraph has remained available mainly for backwards compatibility purposes).
    So to answer your questions, passing of graph parameters from the parent graph to the child graph via RunGraph (using the "Graph parameters to pass" property) is not working properly. As a workaround, you can either use the ExecuteGraph component or a subgraph if your use case allows for it.
    To answer your second question, you can click on the dropdown arrow in the Execution tab in the Designer to get a complete execution hierarchy. Then, just double-click on the graphB which should show the execution log of the graphB in the Console tab.
    Best,
  • Avatar
    balaji.venkatachalam
    0
    Comment actions Permalink
    Thanks Vladimir.

Please sign in to leave a comment.