This message was deleted.

Just a heads up here, there is a bug fix coming up, it may fix this. Also, we plan to add a history verification step before sending the request to litellm, that should catch this kind of issue