Skip to content

🤔 [ISSUE] - finding block logic is prioritizing the first match #866

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
yassinedorbozgithub opened this issue Mar 27, 2025 · 0 comments · May be fixed by #955
Open

🤔 [ISSUE] - finding block logic is prioritizing the first match #866

yassinedorbozgithub opened this issue Mar 27, 2025 · 0 comments · May be fixed by #955
Assignees
Labels
enhancement New feature or request

Comments

@yassinedorbozgithub
Copy link
Collaborator

Description

We can notice that the current logic is prioritizing the first block match even if this block has a global value.

Reproduction steps

1. Choice a custom plugin (starting block) returning an outcome named 'test' for example
2. Create two text blocks
3. Link the two blocks with the custom block via nextBlocks link
4. Add a Any Outcome trigger for the first Block
5. Add a test Outcome trigger for the second Block
6. Trigger the flow
7. Notice that the older matched block has always priority

Logs

Browsers

No response

OS

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants