Skip to content

Errors in Agent Vector DB metadata filter in Agentflow v2 #4979

@jwyoon12

Description

@jwyoon12

Describe the bug

If multiple Agent nodes are present on the same screen, modifying the metadata filter in one node unintentionally applies the same filter value to all other nodes.

To Reproduce

  1. Go to Agentflow v2.
  2. Add two Agent nodes, labeled 1 and 2.
  3. Set a metadata filter on 1’s vector DB, for example: A: 1.
  4. Check 2’s vector DB metadata filter — it will also show A: 1.
  5. Now change 2’s metadata filter to something else, e.g., B: 2.
  6. Go back and check 1 — its metadata filter has now changed to B: 2.

Expected behavior

  1. Go to Agentflow v2.
  2. Add two Agent nodes, labeled 1 and 2.
  3. Set a vector DB metadata filter on 1, for example: A: 1.
  4. Check 2’s metadata filter — it should still be empty.
  5. Now set 2’s metadata filter to B: 2.
  6. Go back and check 1 — it should still have A: 1 as its filter.

Screenshots

No response

Flow

No response

Use Method

Flowise Cloud

Flowise Version

3.0.4

Operating System

None

Browser

Chrome

Additional context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions