New fine-tuning training on davinci-002 — Retired
- Deprecated
- —
- Shutdown
- 2024-10-28
- Status
- deprecated
- Replacement
- gpt-4o-mini
Quick fix — copy & paste
Choose your language. The "before" block matches the deprecated call; the "after" block is the drop-in replacement.
# OpenAI: New fine-tuning training on davinci-002 (deprecated)
model = "New fine-tuning training on davinci-002" # Replacement
model = "gpt-4o-mini" // OpenAI: New fine-tuning training on davinci-002 (deprecated)
const model = "New fine-tuning training on davinci-002"; // Replacement
const model = "gpt-4o-mini"; "model": "New fine-tuning training on davinci-002" "model": "gpt-4o-mini" This migration was generated automatically from the model rename. If your code does more than swap a model id, double-check request/response shapes against the official OpenAI migration guide.
Error messages
Seeing one of these? You're in the right place.
-
model_not_found: New fine-tuning training on davinci-002 -
The model `New fine-tuning training on davinci-002` has been deprecated -
The model `New fine-tuning training on davinci-002` does not exist or you do not have access to it
Replacement options
-
gpt-4o-miniCompare token cost →
Other OpenAI deprecations
What this means for your code
New fine-tuning training on davinci-002 is a fine-tuned model based on a deprecated base model. Fine-tuned models cannot be migrated by changing a string. The base model's deprecation means your fine-tune will stop working. You need to re-fine-tune on a supported base.
New fine-tuning training on davinci-002 was retired by OpenAI on 2024-10-28. API calls now return an error and the model is no longer accessible. New code should use gpt-4o-mini; legacy code that still references this model id needs to be updated immediately.
Find every call in your codebase
Before you change anything, locate every place the deprecated model id is referenced. Search source files, environment files, feature flags, and config repos. Use these commands from your project root:
Python projects
grep -rn '"New fine-tuning training on davinci-002"' --include="*.py" . JavaScript / TypeScript projects
grep -rn '"New fine-tuning training on davinci-002"' --include="*.{js,ts,tsx,jsx}" . Anywhere (configs, scripts, infra)
grep -rn "New fine-tuning training on davinci-002" . Migration checklist
Steps in order. Skip any that don't apply, but read the whole list — for fine tuning models, the non-obvious steps are usually the ones that break in production.
- 1. Identify the deprecated base model used by your fine-tune
- 2. Re-prepare your training data — format may need updating for the new base
- 3. Run a fresh fine-tuning job against a current base model
- 4. Validate the new fine-tune meets your evals before swapping in
- 5. Plan a parallel-run period where both the old and new fine-tunes serve traffic
Will this migration cost more?
Switching from New fine-tuning training on davinci-002 to gpt-4o-mini could change your costs significantly. Calculate the exact difference for your prompts.
Open the cost calculator →