OverrideConfig fails to update custom variable in Agentflow (regression from v3.0.11 to v3.1.3) #6651

Describe the bug

In Flowise v3.0.11, passing custom variables using overrideConfig in an Agentflow API request worked as expected, dynamically updating the target variable during execution.

After upgrading to v3.1.3, using the exact same API call payload no longer overrides the variable's value inside the Agentflow, causing dynamic conditional routing (e.g., classification logic) to break.

To Reproduce

Steps to Reproduce

1. Create an Agentflow that relies on a custom variable (clasificador) with "Override Configuration" turned on.
2. Send a request to the Agentflow API endpoint including overrideConfig:

   {
     "question": "Test query",
     "overrideConfig": {
       "clasificador": "new_value"
     }
   }
   

Expected behavior

The variable clasificador should take the value passed in overrideConfig ("new_value"), as it did in version 3.0.11.

Screenshots

No response

Flow

No response

Use Method

None

Flowise Version

3.1.3

Operating System

Linux

Browser

Chrome

Additional context

No response