Skip to main content
Version: 1.3.0

Continue

Control Flow Pipeline

Synopsis​

Continues to the next processor in the pipeline chain.

Schema​

- continue:
    description: <text>
    if: <script>
    ignore_failure: <boolean>
    ignore_missing: <boolean>
    on_failure: <processor[]>
    on_success: <processor[]>
    tag: <string>

Configuration​

The following fields are used to define the processor:

FieldRequiredDefaultDescription
descriptionN-Explanatory note
ifN-Condition to run
ignore_failureNfalseContinue processing if operation fails
ignore_missingNfalseSkip processing if referenced field doesn't exist
on_failureN-See Handling Failures
on_successN-See Handling Success
tagN-Identifier

Details​

Explicitly continues execution to the next processor in the pipeline sequence. This processor is primarily used for flow control in conditional processing scenarios or to make pipeline logic more explicit.

The continue processor acts as a no-operation that allows pipeline execution to proceed normally. It's useful in conditional blocks where you want to explicitly indicate continuation rather than implicit flow.

note

The continue processor doesn't modify any data or fields. It serves purely as a control flow mechanism to make pipeline logic more readable and explicit.

This processor is most commonly used within conditional logic blocks, success/failure chains, or when you need to clearly indicate that processing should continue despite certain conditions.

warning

While the continue processor doesn't perform any operations itself, it can still trigger success/failure chains if configured, allowing for complex flow control patterns.

Examples​

Basic Continue Usage​

Explicitly continuing pipeline execution...

- if:
    condition: "logEntry.level == 'INFO'"
    processors:
      - continue:
          description: "INFO level logs proceed normally"

allows processing to continue:

{
  "level": "INFO",
  "message": "User logged in"
}

Conditional Continue​

Using continue in conditional logic...

- continue:
    if: "logEntry.status == 'success'"
    description: "Continue processing successful events"
- set:
    field: processed
    value: true

continues only when condition matches:

{
  "status": "success",
  "processed": true
}

Continue with Success Chain​

Triggering additional processing on continue...

- continue:
    description: "Continue and log the action"
    on_success:
      - set:
          field: flow_status
          value: "continued"

executes success chain:

{
  "original_data": "value",
  "flow_status": "continued"
}

Documentation in Complex Flow​

Using continue for pipeline documentation...

- if:
    condition: "logEntry.type == 'audit'"
    processors:
      - continue:
          description: "Audit logs proceed to enrichment"
          tag: "audit_flow_marker"
      - enrich:
          field: user_id
          target: user_info

makes pipeline flow explicit:

{
  "type": "audit",
  "user_id": "123",
  "user_info": {
    "name": "John Doe"
  }
}

Error Handling Flow​

Using continue in error recovery...

- validate:
    field: email
    pattern: ".*@.*"
    on_failure:
      - set:
          field: email_valid
          value: false
      - continue:
          description: "Continue despite invalid email"

continues processing after error handling:

{
  "email": "invalid-email",
  "email_valid": false
}