From 4ea12150fa5c7fe5b6c0442232b3846f71459481 Mon Sep 17 00:00:00 2001 From: Ben Langfeld Date: Tue, 17 Feb 2026 11:41:37 -0300 Subject: [PATCH] Specify updated field name causing premium feature block Without this, the error returned when a user attempts to perform an update to an object (eg a Team) does not specify which field in the update request was considered blocking because of the lack of an enterprise license, making correcting the issue very difficult. --- litellm/proxy/management_endpoints/common_utils.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/litellm/proxy/management_endpoints/common_utils.py b/litellm/proxy/management_endpoints/common_utils.py index 34a17f6c274..715c800fbac 100644 --- a/litellm/proxy/management_endpoints/common_utils.py +++ b/litellm/proxy/management_endpoints/common_utils.py @@ -372,7 +372,7 @@ def _update_metadata_field(updated_kv: dict, field_name: str) -> None: # proceed with the update so that users can intentionally clear a # previously-set field by sending an empty list/dict. if value is not None and value != [] and value != {}: - _premium_user_check() + _premium_user_check(feature: f"update {field_name}") if field_name in updated_kv and updated_kv[field_name] is not None: # remove field from updated_kv