How to get around the cyclic graph problem in this input assignment

We proudly present: The release of DMXControl 3.3.3!


On September 29, 2026, we held our release show for DMXControl 3.3.3. During our usual “hour-long” session, we showed you all the new features in this version and what it now has to offer.
Read all about it in the corresponding news article: We proudly present: The release of DMXControl 3.3.3!

    Hello again DMXcontrol experts.

    I have a question about a cyclic input assignment.

    In the below input assignment (only the orange part is important I think), I want to start a cuelist from a softdesk button only if the cuelist is not already running.
    I cannot, however, make the red connection; the kernel complains about a cyclic input error. I am also unable to add the cuelist to the graph twice, or even add only the relevant subelements (Input GO, output STATE).
    Surely there must be a way around this problem; please advise!

    Hallo DMXcontrol-Experten,

    ich habe eine Frage zu einer zyklischen Eingangszuweisung.

    In der untenstehenden Eingangszuweisung (ich denke, nur der orangefarbene Teil ist relevant) möchte ich eine Cuelist über einen Softdesk-Button nur dann starten, wenn die Cuelist noch nicht läuft. Ich kann jedoch die rote Verbindung nicht herstellen; der Kernel meldet einen Fehler wegen einer zyklischen Eingangszuweisung. Ich kann die Cuelist auch nicht zweimal zum Diagramm hinzufügen oder nur die relevanten Unterelemente (Eingang GO, Ausgang STATE). Es muss doch eine Lösung für dieses Problem geben; bitte um Hilfe!

    Quote


    09:14:43 ERROR Input_gService -
    System.InvalidOperationException: Adding this edges would create a cyclic graph. This is not allowed.
    at org.dmxc.lumos.Kernel.Input.v2.Graph.AddEdges(IEnumerable`1 edges, Boolean processGraph, Boolean reassignLevel) in D:\Jenkins\workspace\Lumos_Pipeline_3.3\Lumos\src\Kernel\Input\v2\Graph\Graph.cs:line 321
    at org.dmxc.lumos.Kernel.Input.v2.Graph.AddEdge(GraphEdge e) in D:\Jenkins\workspace\Lumos_Pipeline_3.3\Lumos\src\Kernel\Input\v2\Graph\Graph.cs:line 308
    at org.dmxc.lumos.Kernel.Net.gService.Input_gService.AddEdge(IGraph g, GraphNodePortID from, GraphNodePortID to) in D:\Jenkins\workspace\Lumos_Pipeline_3.3\Lumos\src\Kernel\Net\gService\Input_gService.cs:line 862

    Thank you both for your suggestions. SInce the cuelist ends itself after "a while", the Play connection makes most sense in that case.

    LightningBrothers Did you mean the following as in the attachement below? That seems to work and do the same as dragging the node onto the connection set. Why is one allowed but not the other!?


    Quote from namezero111111

    Did you mean the following as in the attachement below?

    Yes, exactly.

    Quote from namezero111111

    Why is one allowed but not the other!?

    The exact reason I am not able to explain exactly. Mainly it’s some kind of avoiding direct signal loops.

    With the two nodes adding you can see, you have with this way a signal flow still from left to right. And at least it’s a bit better to follow, how it works.