Start a Graph

    Start a Graph starts a specified graph from a specified sandbox.

    Table 36. Attributes of "Start a graph" task
    Name Description

    Task type

    "Start a graph"

    Start on

    Node(s) to process the task.

    This attribute is accessible only in Cluster environment. If there are nodes specified, the task will be processed on the first node which is online and ready.


    This select box contains sandboxes which are readable for the logged user. Select the sandbox which contains the graph to execute.


    The graph to be executed.

    This select box is filled with all graphs files accessible in the selected sandbox. Type a graph name or path to filter available items.

    Save execution history

    Information about the execution of the graph is saved to database.

    If the task runs too often (once in several seconds), you can increase the database performance by disabling this attribute.

    Pass parameters from the checked graph (jobflow)

    Allows the user to pass parameters from the checked graph (jobflow) to the graph triggered by this event listener.

    Check the option and enter a comma-separated list of parameters to be passed in the newly appeared field.


    A list of parameters passed to the graph.

    Event parameters like EVENT_RUN_RESULT, EVENT_RUN_ID, etc. are passed to the executed job without limitations. The EVENT_RUN_RESULT and EVENT_RUN_ID parameters are used in context of event listeners. They are not used in context of scheduling.

    tasks execute graph
    Figure 173. Web GUI - Graph execution task

    Please note that the behavior of this task type is almost the same as Start a Jobflow.


    You can start a graph with parameters.

    To start a graph with a parameter, choose an existing parameter from the list, set its value, and click the plus sign button at the end of line.

    If the graph is started by an event listener, it receives additional parameters from the triggering job.

    Parameters passed to graph by Event Listeners
    Table 37. Additional parameters available in Event Listeners
    Name Description


    The name of the user who caused the event


    A numeric ID of the user who caused the event.


    A code of the sandbox containing the graph/jobflow


    A sandbox-relative path to the graph/jobflow file.


    The current status of the graph/jobflow execution (N_A, READY, RUNNING, WAITING, FINISHED_OK, ERROR, ABORTED, TIMEOUT or UNKNOWN).


    A numeric ID of the run record representing graph/jobflow execution.


    A graph/jobflow event type that triggered the task.


    A specified timeout (in milliseconds) for the TIMEOUT event to occur