bytechefhq / bytechefhq/bytechef

[feature]: As Workflow Designer I would like to pause execution of component

Open
#3,483 0 comments 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
Java
Stars
1k
Forks
170
Avg merge
11h 25m
Merged PRs (30d)
115

Description

### Tell us about the problem you're trying to solve

As Workflow Designer I would like to pause execution of component without blocking the flow. Imagine I have Logger component that I don't want to execute in PRODUCTION.
It would be perfect if I could pause component either:
- explicitely - I click/set PAUSED FLAG by clicking on component and checking PAUSE checkbox
- implecitly - I use expression language to PAUSE component

### Describe the solution you’d like

Introduce Action property "pausable" or something more business (property name should clearly communicate its purpose).
FRONTEND:
- If pausable, UI should allow presence of Pause Component CHECKBOX.
- If CHECKED - component property editor should be FULLY accessible (property panel and data pill panel are functional) BUT UI must imply that user is working on PAUSED component (red background or WARNING)
- If CHECKED - component in the flow diagram should be either GRAYED or with RED border or other kind of VISUAL DISTRUCTION
- CAN NOT PAUSE Component which Output is used by subsequent components
BACKEND
If pausable property is allowed and set to true, workflow engine should skip that execution.

### Describe the alternative you’ve considered or used

- DUPLICATE existing workflow
- delete component whose execution is unwanted
- save and publish new workflow

### Additional context

_No response_

Contributor guide

Open the contributing guide

Research direction

No files, tests, or entry points are named. Start by locating the workflow designer component editor and flow diagram, then trace the workflow engine execution path. Done means supporting explicit and expression-based pausing, preserving editor access, showing paused state clearly, preventing pauses when outputs are used downstream, and skipping execution safely.

Written by the indexing model from the issue text.

Assessment

Domain
full-stack
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.