AI-generated Key Takeaways
- 
          The document provides a list of possible errors related to media files. 
- 
          Errors cover various issues such as invalid IDs, types, data conflicts, and service unavailability. 
- 
          The errors are presented as an enum with descriptions of each potential problem. 
Enum describing possible media file errors.
| Enums | |
|---|---|
| 
 | Enum unspecified. | 
| 
 | The received error code is not known in this version. | 
| 
 | Cannot create a standard icon type. | 
| 
 | May only select Standard Icons alone. | 
| 
 | Image contains both a media file ID and data. | 
| 
 | A media file with given type and reference ID already exists. | 
| 
 | A required field was not specified or is an empty string. | 
| 
 | A media file may only be modified once per call. | 
| 
 | Field is not supported for the media sub type. | 
| 
 | The media file ID is invalid. | 
| 
 | The media subtype is invalid. | 
| 
 | The media file type is invalid. | 
| 
 | The mimetype is invalid. | 
| 
 | The media reference ID is invalid. | 
| 
 | The YouTube video ID is invalid. | 
| 
 | Media file has failed transcoding | 
| 
 | Media file has not been transcoded. | 
| 
 | The media type does not match the actual media file's type. | 
| 
 | None of the fields have been specified. | 
| 
 | One of reference ID or media file ID must be specified. | 
| 
 | The string has too many characters. | 
| 
 | The specified type is not supported. | 
| 
 | YouTube is unavailable for requesting video data. | 
| 
 | The YouTube video has a non positive duration. | 
| 
 | The YouTube video ID is syntactically valid but the video was not found. |