V4 API metadata retrieval returns 500 Internal Server Error on some assets

Help
,
1

Hi, I couldn’t seem to find anything about this, but I constantly get 500 internal server error when using the “GET Show metadata for asset” and seems to be the only endpoint I have issues with.

It only happens on some files, and it seems to be files where someone has updated the custom fields on Frame.io via the browser. The same asset returns all data as usual for every other API call.

The PATCH metadata works fine, and the only “fix” for my problem I’ve found is using the API to wipe all the custom fields and start again.

The problem is that if I have 100 assets all with 20 different custom metadata fields, then having to add all that data back in takes a long time, as the only way I can do this is by looking via the web and manually writing down all the tags etc, then wiping all custom fields via the API and updating with the old tags. Quite painful!

Has anyone else run into this same issue? I’m using the V4 API — testing with postman when my python scripts return errors to confirm it has the exact same error.

Support had no idea what was going on, but said the metadata must be “malformed” — so not sure why the browser metadata updates would “malform” the metadata on the database? And why is it only an issue with the metadata and nothing else? Help please!

2

hi @videoeditorperson can you DM me the response you get (and your curl command) and the asset_ids of the problem assets with the get show metadata for those asssets? That will help us troubleshoot.

3

Thanks @CharlieAnderson , but I’m afraid I’m new here and can’t see any direct messaging capabilities?

If you are a moderator maybe you can see my email address?

{{BASE_URL}}/v4/accounts/:account_id/files/:file_id/metadata?show_null=true

{
    "errors": [
        {
            "detail": "Internal Server Error"
        }
    ]
}

(EDIT: I have been granted DM’ing rights after using the forum enough it seems)