Skip to content
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

[BUG] Custom Tool Override Configuration Broken in Flowise v2.2.3 #3857

Closed
heslanx opened this issue Jan 13, 2025 · 0 comments · Fixed by #3875
Closed

[BUG] Custom Tool Override Configuration Broken in Flowise v2.2.3 #3857

heslanx opened this issue Jan 13, 2025 · 0 comments · Fixed by #3875
Labels
bug Something isn't working

Comments

@heslanx
Copy link

heslanx commented Jan 13, 2025

Describe the bug
In Flowise version 2.2.3, the ability to override custom tool configurations using overrideConfig.customToolName, overrideConfig.customToolDesc and overrideConfig.customToolShema is not functioning as expected.

To Reproduce
Steps to reproduce the behavior:

  1. Open Postman
  2. Create a POST request to https://your-flowise-url.com/api/v1/prediction/{flow-id}
  3. Set headers:
    • Content-Type: application/json
  4. Send the request with the following payload:
{
  "question": "Qual a melhor estratégia para aumentar minhas vendas?",
  "overrideConfig": {
    "sessionId": "chat_12345",
    "vars": {
      "contactId": "contact_98765"
    },
    "systemMessage": "Você é um assistente.",
    "customToolName": {
      "customTool_0": "TESTE"
    },
    "customToolDesc": {
      "customTool_0": "Teste da tool 0"
    }
  },
  "history": [
    {
      "role": "user",
      "content": "Preciso aumentar minhas vendas"
    },
    {
      "role": "assistant", 
      "content": "Entendo. Vamos analisar algumas estratégias."
    }
  ]
}
  1. Observe that the custom tool name and description are not being overridden

CleanShot 2025-01-12 at 21 05 08@2x

Yes, the option to allow override was already enabled in the new version.

Expected behavior
The customToolName, customToolDesc and customToolShema in overrideConfig should dynamically modify the name and description of the custom tool with the key customTool_0.

  • In previous version's (2.1.3) successful override
    CleanShot 2025-01-12 at 21 34 53@2x

Setup

  • Flowise Version: 2.2.3
  • Testing Method: Postman API Request
  • Environment: Web-based Flowise instance

Curl Request

curl --location 'https://your-flowise-url.com/api/v1/prediction/{flow-id}' \
--header 'Content-Type: application/json' \
--data '{
  "question": "Qual a melhor estratégia para aumentar minhas vendas?",
  "overrideConfig": {
    "customToolName": {
      "customTool_0": "TESTE"
    },
    "customToolDesc": {
      "customTool_0": "Teste da tool 0"
    }
  }
}'

Additional Context

  • Confirm the override mechanism worked in previous versions
  • Verify if this is a breaking change in the API
  • Check if the issue is specific to certain custom tool configurations

Potential Impact
This bug prevents dynamic customization of tool names and descriptions, which could affect workflow flexibility and user experience.

Proposed Solution

  • Restore the previous override mechanism
  • Provide clear documentation on current method for tool configuration
  • Add backward compatibility for existing override methods
@HenryHengZJ HenryHengZJ added the bug Something isn't working label Jan 15, 2025
@HenryHengZJ HenryHengZJ linked a pull request Jan 15, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants