api-1 | 2026-04-29 16:17:20.435 ERROR [Dummy-482] [delete_tool_parameters_cache_when_sync_draft_workflow.py:41] 30ed488ad5f554c1a2c0ccd4ece7a98d - Failed to delete tool parameters cache for workflow aa8d4ea7-ab70-4438-8f29-0121dcd2dada node 1770287492505 api-1 | Traceback (most recent call last): api-1 | File "/app/api/events/event_handlers/delete_tool_parameters_cache_when_sync_draft_workflow.py", line 22, in handle api-1 | tool_entity = ToolEntity.model_validate(node_data["data"]) api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ api-1 | File "/app/api/.venv/lib/python3.12/site-packages/pydantic/main.py", line 716, in model_validate api-1 | return cls.pydantic_validator.validate_python( api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ api-1 | pydantic_core._pydantic_core.ValidationError: 1 validation error for ToolEntity api-1 | tool_configurations api-1 | Value error, ensure_ascii must be one of: str, int, float, bool [type=value_error, input_value={'ensure_ascii': {'type':...nstant', 'value': True}}, input_type=dict] api-1 | For further information visit https://errors.pydantic.dev/2.12/v/value_error

TL;DR

The issue is likely due to a validation error in the tool_configurations data model, where the ensure_ascii value is expected to be a primitive type (str, int, float, bool) but is instead an object with type and value keys.

Guidance

• The error message indicates a validation error in the ToolEntity model, specifically with the ensure_ascii field in the tool_configurations dictionary.
• The ensure_ascii value is being passed as an object {"type": "constant", "value": false} instead of a primitive boolean value false.
• To fix this, the frontend should pass the ensure_ascii value as a boolean primitive, e.g., "ensure_ascii": false.
• Verify that the tool_configurations data model is correctly defined in the ToolEntity model to accept the expected data types.

Example

# Expected data model
tool_configurations = {
    "ensure_ascii": False
}

# Incorrect data model
tool_configurations = {
    "ensure_ascii": {
        "type": "constant",
        "value": False
    }
}

Notes

The issue seems to be related to a change in the tool_configurations data model or the validation rules in the ToolEntity model. Without more information about the model definitions, it's difficult to provide a more specific solution.

Recommendation

Apply workaround: Update the frontend to pass the ensure_ascii value as a boolean primitive, and verify that the tool_configurations data model is correctly defined in the ToolEntity model.