Skip to content

[BUG] Interrupt-before switch becomes disabled when setting node as entry point; pipeline immediately triggers interruption #3645

@MarunNexit

Description

@MarunNexit

Description of problem:
When "interrupt before" is set on a node and that node is made the pipeline entry point, the UI disables the interrupt-before switch (cannot be toggled) while still showing that the node is interrupted; running the pipeline then immediately triggers the interruption


Steps to Reproduce:

  1. Enable the "interrupt before" option on any pipeline node.
  2. Set the same node as the pipeline entry point.
  3. Observe the state of the interrupt-before toggle in the UI.

Expected Result:
One of the following behaviors should occur:

  1. The interruption setting is automatically disabled and removed from the YAML configuration when the node becomes the entry point.
    or
  2. The interrupt-before toggle remains enabled and editable, clearly displaying its current state and allowing the user to manually change it.

Actual Result:

  • The interrupt-before toggle becomes disabled (non-editable) in the UI.
  • The UI still indicates that the interruption is active.
  • In YAML the interruption still presents
  • When the pipeline is executed, the interruption is triggered immediately.

Link(s) to Reproduce:
https://dev.elitea.ai/app/406/pipelines/all/352?viewMode=owner&name=InterruptionBeforeBug&isFromCreation=true

Stage/Next env
Image

Dev env
Image

Metadata

Metadata

Labels

feat:pipeline_nodesPipeline nodes feature.feat:pipelinesPipelines feature: create/run pipelines, config, outputs and history.nfr:usabilityUsability/UX friction (flows, copy, clarity).

Type

Projects

Status

Bugs

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions