Skip to content

Element is not connected check #11

Description

@raulmonti

When I first place an task inside a component, I get the message element not connected. I understand that this means the task does not belong to a flow starting at the start event of the component. Am I wrong there? Anyways, when I connect another task as an output to this initial task, the message goes away, although none of the two tasks belong to a flow now. I understand the message should only go away if I can find a path from the initial event of the component to the task. If this is too hard/ineficient to check an alternative is to show the message if there is no input flow to the task.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions