LiteLLM Azure gpt-image-2 Edit Fails with TypeError in v1.84.0

What this error means

AzureException APIError - '<=' not supported between instances of 'str' and 'int'. Received Model Group=gpt-image-2 is a LiteLLM failure pattern reported for developers trying to fix litellm azure gpt-image-2 edit error type comparison. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

LiteLLM proxy /image/edits endpoint fails with 500 error when proxying Azure gpt-image-2 model. TypeError: ’<=’ not supported between ‘str’ and ‘int’ in v1.84.0. Regression from previous version.

Common causes

• Developers using Azure OpenAI image generation through LiteLLM proxy hit this when upgrading to v1.84.0; blocks image editing workflows in production
• LiteLLM proxy /image/edits endpoint fails with 500 error when proxying Azure gpt-image-2 model. TypeError: ’<=’ not supported between ‘str’ and ‘int’ in v1.84.0. Regression from previous version.

Quick fixes

1. Confirm the exact error signature matches AzureException APIError - '<=' not supported between instances of 'str' and 'int'. Received Model Group=gpt-image-2.
2. Check the LiteLLM account, local tool state, and provider configuration involved in the failing workflow.
3. Compare the failing environment with a known working setup, then change one configuration value at a time.

Platform/tool-specific checks

• Verify the command, editor, extension, or API client that produced the error.
• Compare local settings with CI, deployment, or editor-level settings when the error appears in only one environment.
• Avoid deleting credentials, local model data, or project settings until the failing scope is clear.

Step-by-step troubleshooting

1. Capture the exact error message and the command, editor action, or request that triggered it.
2. Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
3. Review the source evidence below and compare it with your environment.
4. Apply one change at a time and rerun the smallest failing action.
5. Keep the working fix documented for the team or deployment environment.

How to prevent it

• Keep provider/tool configuration documented.
• Record non-secret diagnostics such as tool version, provider name, model name, and command path.
• Add a lightweight check before CI or production workflows depend on the tool.

Sources checked

• https://github.com/BerriAI/litellm/issues/27978

Evidence note: LiteLLM proxy /image/edits endpoint fails with 500 error when proxying Azure gpt-image-2 model. TypeError: ’<=’ not supported between ‘str’ and ‘int’ in v1.84.0. Regression from previous version.

Related errors

• LiteLLM Azure OpenAI integration
• gpt-image-2 API errors
• LiteLLM proxy image generation

FAQ

What should I check first?

Start with the exact AzureException APIError - '<=' not supported between instances of 'str' and 'int'. Received Model Group=gpt-image-2 text and the smallest action that reproduces it.

Can I ignore this error?

No. Treat it as a failed LiteLLM workflow until the root cause is understood.

Is this guaranteed to have one fix?

No. The imported evidence supports the troubleshooting path above, but tool behavior can vary by account, plan, version, provider, and local configuration.

How do I know the fix worked?

Rerun the same command, editor action, or request. The fix is working when that action completes without AzureException APIError - '<=' not supported between instances of 'str' and 'int'. Received Model Group=gpt-image-2.