Continue If¶

Conditionally control workflow execution by evaluating custom logic statements and either continuing to specified next steps or terminating the current branch based on the condition result, enabling dynamic branching, conditional processing, and workflow control flow.

How This Block Works¶

This block evaluates a conditional statement and controls whether the workflow branch continues execution or stops. The block:

1. Takes a conditional statement (using a query language syntax) and evaluation parameters as input
2. Builds an evaluation function from the conditional statement definition
3. Evaluates the condition using the provided evaluation parameters (which can reference workflow inputs, step outputs, or other dynamic values)
4. If the condition evaluates to true:
5. Continues execution to the specified next_steps blocks
6. If a stop_delay is configured, records the current time to enable delayed termination
7. If the condition evaluates to false:
8. Terminates the current workflow branch (stops execution of downstream blocks in this branch)
9. If stop_delay was previously triggered and the delay period hasn't elapsed, continues execution to next_steps for the remaining delay duration
10. Returns flow control directives that either continue execution to the next steps or terminate the branch

The block uses a query language system that supports binary comparisons (equality, inequality, greater than, less than, etc.) between dynamic values (from workflow data) and static values. Conditions can check numeric values, string values, or other data types. The stop_delay feature allows the branch to remain active for a short period after a condition becomes false, which is useful for handling transient states or maintaining execution during brief condition fluctuations (e.g., keeping a workflow active for a few seconds after a detection count drops below threshold).

Common Use Cases¶

• Conditional Processing Based on Detection Counts: Continue processing only when the number of detected objects exceeds a threshold (e.g., process alerts only when 3+ objects are detected, skip processing when count is below threshold)
• Dynamic Quality Control: Evaluate image quality metrics, detection confidence scores, or model outputs and continue workflow execution only when quality criteria are met, terminating branches that don't meet standards
• Conditional Notifications: Send notifications or trigger actions only when specific conditions are met (e.g., continue to notification blocks when confidence scores are above 0.9, or when specific object classes are detected)
• Branch Filtering and Routing: Route workflow execution to different branches based on dynamic conditions, allowing one path to continue while others terminate (e.g., continue video recording branch when motion is detected, terminate when no activity)
• Threshold-Based Actions: Execute downstream blocks only when values meet thresholds (e.g., continue to data storage when detection count > 5, terminate otherwise; continue processing when temperature > threshold, skip when below)
• Transient State Handling: Use stop_delay to handle brief condition changes by keeping branches active for a short period after conditions become false, preventing rapid on/off toggling in response to temporary fluctuations

Connecting to Other Blocks¶

This block controls workflow execution flow and can be connected:

• After detection or analysis blocks (e.g., Object Detection, Classification, Keypoint Detection) to evaluate detection counts, confidence scores, class names, or other prediction results and conditionally continue processing based on the analysis results
• After data processing blocks (e.g., Property Definition, Expression, Delta Filter) to evaluate computed values, metrics, or processed data and control whether subsequent blocks execute based on the processed results
• Before notification blocks (e.g., Email Notification, Slack Notification, Twilio SMS Notification) to conditionally trigger notifications only when specific conditions are met, preventing unnecessary alerts
• Before data storage blocks (e.g., Local File Sink, CSV Formatter, Roboflow Dataset Upload, Webhook Sink) to conditionally save or send data only when certain criteria are satisfied, filtering what gets stored or transmitted
• Between workflow stages to create conditional processing paths, where different branches execute based on dynamic conditions, enabling complex workflow logic and decision trees
• In parallel branches to create multiple conditional paths, allowing different parts of a workflow to continue or terminate independently based on their respective conditions

Type identifier¶

Use the following identifier in step "type" field: roboflow_core/continue_if@v1to add the block as as step in your workflow.

Properties¶

The Refs column marks possibility to parametrise the property with dynamic values available in workflow runtime. See Bindings for more info.

Available Connections¶

Input and Output Bindings¶

The available connections depend on its binding kinds. Check what binding kinds Continue If in version v1 has.

{
    "name": "<your_step_name_here>",
    "type": "roboflow_core/continue_if@v1",
    "condition_statement": {
        "statements": [
            {
                "comparator": {
                    "type": "(Number) =="
                },
                "left_operand": {
                    "operand_name": "left",
                    "type": "DynamicOperand"
                },
                "right_operand": {
                    "type": "StaticOperand",
                    "value": 1
                },
                "type": "BinaryStatement"
            }
        ],
        "type": "StatementGroup"
    },
    "evaluation_parameters": {
        "left": "$inputs.some"
    },
    "next_steps": [
        "$steps.on_true"
    ],
    "stop_delay": 5
}