UUM-149444
Fixed in 6000.7.0b3Mentioned in 8 release notes.
First fixed in 6000.7.0b3 (Oct 5, 2026); relisted in 7 later releases.
| Version | Section | Risk | Impact | Note |
|---|---|---|---|---|
| 7000.0.0a16 | Fixes Asset Pipeline | Fix | Fixed a spurious error message "Failed to update AssetBundle names in the database" that can succeed on an automatic retry. | |
| 7000.0.0a12 | Fixes Asset Pipeline | Fix | Fixed a spurious error message "Failed to update AssetBundle names in the database" that can succeed on an automatic retry. | |
| 7000.0.0a11 | Fixes Asset Pipeline | Fix | Fixed a spurious error message "Failed to update AssetBundle names in the database" that can succeed on an automatic retry. | |
| 7000.0.0a10 | Fixes Asset Pipeline | Fix | Fixed a spurious error message "Failed to update AssetBundle names in the database" that can succeed on an automatic retry. | |
| 7000.0.0a9 | Fixes Asset Pipeline | Fix | Fixed a spurious error message "Failed to update AssetBundle names in the database" that can succeed on an automatic retry. | |
| 7000.0.0a8 | Fixes Asset Pipeline | Fix | Fixed a spurious error message "Failed to update AssetBundle names in the database" that can succeed on an automatic retry. | |
| 7000.0.0a7 | Fixes Asset Pipeline | Fix | Fixed a spurious error message "Failed to update AssetBundle names in the database" that can succeed on an automatic retry. | |
| 6000.7.0b3 | Fixes Asset Pipeline | Fix | Fixed a spurious error message "Failed to update AssetBundle names in the database" that can succeed on an automatic retry. (UUM-149444) First seen in 6000.7.0a5. |