Troubleshoot activation and validation
Recover from a missing primary trigger, duplicate activation attempt, cycle, or incomplete required setting.
A ready graph has exactly one primary activation that matches its permanent mode. Start with the specific validation issue, select it to focus the affected node or edge when available, and fix that cause. A zero-error count alone does not guarantee that a chosen historical period will produce an Alert or trade.
Primary activation is missing
An ordinary new strategy already contains its primary. If an imported or damaged graph reports none, identify its mode first: Tactical requires Event Trigger and Portfolio requires Schedule Trigger. Add the appropriate primary if the editor offers that repair, configure it, and reconnect the intended control path. Safety Trigger cannot resolve a missing Portfolio primary because it is an auxiliary guard. If the editor cannot repair the imported graph, preserve the current version and review Reset a Flow safely before starting again; reset removes the working nodes and edges.
A trigger was replaced
A primary changes only through the explicit Replace primary action. Adding or pasting a second primary is disabled, and the last one cannot be deleted in an ordinary editable graph. If you replaced it unintentionally, use Undo while the edit is still in the current session. Otherwise configure the replacement and trace every outgoing control edge again; replacement does not prove downstream event settings still match.
The graph contains a cycle
Follow the highlighted edge from source to target and find where the path returns to an earlier executable node. Remove that return edge, then rebuild the behavior as a forward path. Delay does not make a control cycle valid. If you intended to wait for another event, use a supported continuation such as Delay or Await Order Event on a valid forward path; neither starts a new primary.
A required setting is incomplete
Select the referenced node and open Parameters. Complete the field named by the diagnostic, including any dependent control revealed by an earlier choice. For example, Condition with a literal right source uses its literal value, while a port source requires a compatible Right edge. Then review Data Ports: changing parameters can reveal or hide a port and leave an existing connection inactive. Validate again, save only after the graph is ready for the intended action, and use connection troubleshooting if a handle still refuses the edge.
Related documentation
- How a strategy starts and continuesUnderstand primary activation, control outcomes, and why data alone does not execute an action.
- Fix validation issuesUse the validation area to locate a blocking problem, correct it, and confirm that it is resolved.
- Validation and readinessDistinguish blocking errors from guidance and make a graph ready before testing it.